...@sybase.com
Sybase, Inc
From:
Clinton Begin clinton.be...@gmail.com
To:
user-java@ibatis.apache.org
Date:
07/28/2009 06:10 AM
Subject:
Re: LazyLoading and CGLIB return wrong types
You'll have to paste it in, as attachements get stripped.
I think I've seen it before though
that solve your issue?
Chris Mathrusse
christopher.mathru...@sybase.com
Sybase, Inc
From:
Dawson Lewis hardcore...@yahoo.com.br
To:
user-java@ibatis.apache.org
Date:
07/29/2009 12:09 AM
Subject:
Re: LazyLoading and CGLIB return wrong types
Hi,
I am aware
that are generated by CGLIB. Wouldn't
that solve your issue?
Chris Mathrusse
christopher.mathru...@sybase.com
Sybase, Inc
From:
Dawson Lewis hardcore...@yahoo.com.br
To:
user-java@ibatis.apache.org
Date:
07/29/2009 12:09 AM
Subject:
Re: LazyLoading and CGLIB return wrong types
Begin clinton.be...@gmail.com
To:
user-java@ibatis.apache.org
Date:
07/28/2009 06:10 AM
Subject:
Re: LazyLoading and CGLIB return wrong types
You'll have to paste it in, as attachements get stripped.
I think I've seen it before though, a bunch of $adfweragvav type fields.
I wish
Yea, your best bet is to disable lazy loading.
-Original Message-
From: Dawson Lewis [mailto:hardcore...@yahoo.com.br]
Sent: Wed 7/29/2009 1:09 AM
To: user-java@ibatis.apache.org
Subject: Re: LazyLoading and CGLIB return wrong types
Hi,
I am aware of that , but there are so many
help
much with CGLIB generated classes.
Chris Mathrusse
christopher.mathru...@sybase.com
Sybase, Inc
From:
Clinton Begin clinton.be...@gmail.com
To:
user-java@ibatis.apache.org
Date:
07/28/2009 06:10 AM
Subject:
Re: LazyLoading and CGLIB return wrong types
You'll have to paste
by CGLIB. Wouldn't
that solve your issue?
Chris Mathrusse
christopher.mathru...@sybase.com
Sybase, Inc
From:
Dawson Lewis hardcore...@yahoo.com.br
To:
user-java@ibatis.apache.org
Date:
07/29/2009 12:09 AM
Subject:
Re: LazyLoading and CGLIB return wrong types
Hi,
I am aware
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
You'll have to paste it in, as attachements get stripped.
I think I've seen it before though, a bunch of $adfweragvav type fields. I
wish there was a way in XStream to ignore fields that start with $ or
something. You'd have the same problem with any framework that uses CGLIB
or ASM etc.
I've
Hi,
Do you have any clue in how to do that ?
I created a clone method for the Address class so every object is cloned
before it is serialized. It works fine but do you think this is a good idea
?
Best Regards
Stelio
Larry Meadors wrote:
You should be able to, yeah.
Larry
On Thu,
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
Thanks for you reply Larry,
Is there a way I can get the normal Address objects ? I need to serialize
those objects to XML , the extra fields in these enhanced classes will
create problems when deserializing because maybe the application that will
deserialize is not using iBatis. Can't I just
You should be able to, yeah.
Larry
On Thu, Jul 23, 2009 at 12:39 AM, Dawson Lewishardcore...@yahoo.com.br wrote:
Thanks for you reply Larry,
Is there a way I can get the normal Address objects ? I need to serialize
those objects to XML , the extra fields in these enhanced classes will
They are still Address objects, just enhanced ones.
Larry
On Wed, Jul 22, 2009 at 7:58 AM, Dawson Lewishardcore...@yahoo.com.br wrote:
Hi ,
I have an object with a List property - ListAddress addresses, after
iBatis populates this object the addresses fields will not contain a list
of
14 matches
Mail list logo
