While I get the feeling that toplink error messages beat out
hibernate's, I think that messages like the following are pretty much
useless.
The first reaction I have when I see this is.. Why is toplink throwing
a nullPointerException... shouldn't it be in control? Also.. this
tells me nothing about what is going on.
These sorts of errors arise when attempting to access a Remote
entity's member collection with fetchtype Lazy & is no longer attached
to a persistance context. Can't toplink be a little smarter?
Thank you -
Matt
Caused by: java.lang.NullPointerException
at oracle.toplink.essentials.internal.indirection.UnitOfWorkValueHolder.instantiate(UnitOfWorkValueHolder.java:217)
at oracle.toplink.essentials.internal.indirection.DatabaseValueHolder.getValue(DatabaseValueHolder.java:82)
at oracle.toplink.essentials.indirection.IndirectList.buildDelegate(IndirectList.java:193)
at oracle.toplink.essentials.indirection.IndirectList.getDelegate(IndirectList.java:315)
at oracle.toplink.essentials.indirection.IndirectList$1.<init>(IndirectList.java:410)
at oracle.toplink.essentials.indirection.IndirectList.iterator(IndirectList.java:409)
at org.apache.taglibs.standard.tag.common.core.ForEachSupport.toForEachIterator(ForEachSupport.java:348)