Hi,
It is what I am doing , I am using xStream 1.3  for serializing , I was
using the 1.3.1 version before but it could not serialize synchronized
collections , then I switch to 1.3. It seems that xStream is also
serializing those objects created by iBatis at runtime . Have a look at the
xml file generated by xStream , see how much "garbage" (meaning no
disrespect for either iBatis or xStream because I love them both) is being
added.

I do not want to serialize  these iBatis enhanced objects  .

Regards,
Stelio


Have you tried serializing to XStream or another alternative, instead of
using Java's serialization?  While this is a limitation of iBATI 2 (version
3 solves it somewhat, but still not between systems), you should never
depend on Java serialization for connecting two systems.  You should choose
a more canonical serialization process.  XStream is my personal favourite,
but there are many others (even some binary).

Java serialization is a bad thing to depend upon.

Cheers,
Clinton

-- 
View this message in context: 
http://www.nabble.com/LazyLoading-and-CGLIB-return-wrong-types-tp24607048p24694842.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

Reply via email to