Note that the dynamic proxies used in that byte-code manipulation are also not
serializable, so you can get NotSerializableExceptions on shutdown of the container. I
turned off lazy-loading because of that.
This whole issue is kind of a drag. I don't really see when I'll ever be able to use lazy
loading. Well, I guess if I was a good boy and strictly used the request... er, no, cuz
then the whole object graph is going to get re-pulled on every request. So, lazy-loading
is effectively useless(?).
Hmm, I wonder if making your child object variables transient would solve all this.
Although, then they would get ignored on serialization and you would not have the proxies
on de-serialization, resulting in perhaps strange null pointer issues.
Anyone thought about/played with this?
b
Joe Wolf wrote:
Yes, I disabled lazy loading (I didn't know it was on by default) and it
stopped behaving this way. I guess in order to support lazy loading, iBATIS
does some byte code manipulation. Thanks.
-Joe
On January 27, 2006, Larry Meadors wrote:
Looks like an issue with lazy loading..can you try it without and see
if it fixes the issue?
Larry
____________________
Joe Wolf - Software Engineer
CompSci Resources, LLC
703-750-3547
