All the formatting was eaten by scarab, which of course makes stack traces illegible. Again I am posting my bug here where it might be possbile to understand it.
I had JDO working fine with a protype web app that just had a single PC class. I added a second PC class that is supposed to manage Id's across my application. Since the next ID number needs to persist it is a JDO enhanced class as well. I suspect however it gets used substantially earlier in the program, since it is referenced in several class initializers. Now I am getting the following Exception when my IdManager class tries to use an extent to get a list of instances (of class IdManager). Each instance manages Id's for a single PC class. Before reporting this I upgraded to the cvs checkout of RC5 (was using CVS of RC4 compiled somewhere around 12/1) Both versions have this problem. I tweaked the build to give you line numbers for the OJB stuff too.
java.lang.ExceptionInInitializerError
at org.cs101.fdb.impl.jdo.JDOFactory.createLocation(JDOFactory.java:32)
at org.cs101.fdb.test.LocationTest.setUp(LocationTest.java:46)
Caused by: java.lang.NullPointerException
at org.apache.ojb.jdori.sql.OjbExtent.<init>(OjbExtent.java:98)
at org.apache.ojb.jdori.sql.OjbStoreManager.getExtent(OjbStoreManager.java:251)
at com.sun.jdori.common.PersistenceManagerImpl.getExtent(Unknown Source)
at com.sun.jdori.common.PersistenceManagerWrapper.getExtent(Unknown Source)
at org.cs101.fdb.impl.jdo.IdManager.findIdManager(IdManager.java:63)
at org.cs101.fdb.impl.jdo.LocationImpl.<clinit>(LocationImpl.java:51)
... 11 more
Looking at the code It seems that OjbStoreManager is calling connector.getBroker and getting null which it is then passing to the OjbExtent constructor.
-Gus
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
