Hi, I noticed that this question was asked a few years ago with Ibatis 2.X without any resolution.
Basically, lazy loaded objects are enhanced with byte-code generation. The enhanced object/proxy is not serializable even though the source object is. This obviously plays havoc with web applications if the source object is stored in the session. A very simple and probably often used scenario would be a user object that contains a contact object which contains a location, etc.., stored in the session after authentication. Lazy loading can be very useful in situations like this, but the session cannot be serialized to disk by the container (e.g. Tomcat). This negates clustering, for one, thing, and is also a pain for development, as the context is often reloaded due to code changes. Without the serialization support, the developer must plow through the entire log on and resulting work-flow to get to the required web page again. Are there any technical or architectural issues around making the enhanced object serializable? Has anyone else run into this problem? Right now, I've disabled lazy loading to allow the session to be serialized. Thanks, Mike -- View this message in context: http://old.nabble.com/Ibatis-3---Lazy-Loading-and-Serializable-Sessions-tp28442042p28442042.html Sent from the iBATIS - User - Java mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: user-java-unsubscr...@ibatis.apache.org For additional commands, e-mail: user-java-h...@ibatis.apache.org
