Re: [SOLVED] Re: empty optional to-many relations
Ray Kiddy <[email protected]>
| Newsgroups | gmane.comp.web.webobjects.devel |
|---|---|
| Message-ID | <[email protected]> |
It was a simple fix. Sorry about that. I'll look for other NullPointerException bugs in Radar and see if there is anything similarly brain-dead to fix. thanx - ray <rdar://problem/4697851> isValidQualifierType in JDBCAdaptor does not check for NULL typeName On Aug 14, 2006, at 12:34 PM, Zak Burke wrote: > Timo Hoepfner wrote on 8/14/06 3:07 PM: >> Am 14.08.2006 um 20:24 schrieb Zak Burke: >> >>> <com.webobjects.appserver._private.WOComponentRequestHandler>: >>> Exception >>> occurred while handling request: >>> java.lang.NullPointerException >>> DEBUG [2006-08-14 13:58:39,270] (LogPrintStream.java:96) - >>> java.lang.NullPointerException >>> at >>> com.webobjects.jdbcadaptor.JDBCAdaptor.isValidQualifierType >>> (JDBCAdaptor.java:659) >>> >>> at >>> com >>> .webobjects >>> .eoaccess.EODatabaseContext.isValidQualifierTypeForAttribute >>> (EODatabaseContext.java:5174) >> >> I had exactly that a few weeks ago. I was banging my head onto the >> desk >> for several hours (not that it helped...) Finally it turned out, that >> somehow either the "valueClassName" (e.g. "NSNumber") or the >> "valueType" >> (e.g. "i") was empty for some arbitrary numeric attribute of an >> Entity. >> Double-check every attribute of the Entities you suspect to be >> related. > > Wow. That was it -- I had added a new attribute to an entity and > hadn't > specified its External Type. I'm impressed that you figured out the > root > of the problem! > > This wins my vote for "Exception that is least related to its cause." > I was lost down a different rabbit hole entirely, as this certainly > wasn't what it seemed. > > Thanks for the help, > > zak. > _______________________________________________ > WebObjects-dev mailing list > [email protected] > http://www.omnigroup.com/mailman/listinfo/webobjects-dev