I hope that I'm not readdressing an issue that has seen previous resolution,
however, I did search the archives and found no similar entries which
reached resolution.
I have several objects, which contain collections of lazy-loaded siblings.
Whenever I load the parent object, but fail to iterate over the child
collections to load them as well, but rollback or close the transaction in
progress, I get the following stack trace:
java.lang.NullPointerException: Adding null value is not allowed
at org.exolab.castor.persist.FieldMolder.addValue(Unknown Source)
at org.exolab.castor.persist.CollectionProxy$ColProxy.add(Unknown
Source)
at org.exolab.castor.persist.ClassMolder.revertObject(Unknown
Source)
at org.exolab.castor.persist.LockEngine.revertObject(Unknown Source)
at org.exolab.castor.persist.TransactionContext.rollback(Unknown
Source)
at org.exolab.castor.jdo.engine.DatabaseImpl.close(Unknown Source)
at
com.itn.integration.afg.Outbound_850.createOrder(Outbound_850.java:256)
at
com.itn.integration.afg.Outbound_850.processEntry(Outbound_850.java:380)
at
com.itradenetwork.mdf.MessageDrivenProcess.run(MessageDrivenProcess.java:190
)
I've tired implementing the latest release (castor-0.9.4.1) but am still
having the same problem. I imagine this has to be a fairly common issue.
Does anyone know of a fix, without having to load all of my objects before
rolling back?
Thanks for any feedback.
-john:m
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
