java.lang.NullPointerException
at org.exolab.castor.jdo.engine.SQLEngine.store(SQLEngine.java:924)
at org.exolab.castor.persist.ClassMolder.store(ClassMolder.java:1613)
at org.exolab.castor.persist.LockEngine.store(LockEngine.java:756)
at org.exolab.castor.persist.TransactionContext.prepare(TransactionContext. java:1545)
at org.exolab.castor.jdo.engine.DatabaseImpl.commit(DatabaseImpl.java:495)
at com.wow.framework.dao.jdo.impl.AbstractJDOLoader.release(AbstractJDOLoad er.java:69)
at com.wow.framework.dao.jdo.impl.DAOFactory.updateUser(DAOFactory.java: 457)
at com.wow.framework.dao.impl.PluggableDAOFactory.updateUser(PluggableDAOFa ctory.java:252)
at com.wow.framework.dao.User.update(User.java:107)
at com.wow.webapp.pageComponents.registration.TermsAndConditionsPageCompone nt.init(TermsAndConditionsPage
Component.java:91)
Looking at it, lock.invalidate doesn't get called because it's neither an ObjectModifiedException nor a PersistenceException - thinking that's the culprit...
As for what's causing that NPE? Not a clue. Wish I knew, as it's driving me nuts. However, it gives a stream of completely unrelated errors when it dies, that's for sure. Again, there was a constraints violation (would be nice if I could tell castor, somehow, that when an integer value is 0, it should instead use null...), but this particular instance isn't related to that particular problem. Don't know quite what the problem is yet, of course...
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
