ze it with a different delegator. I put warnings in the JavaDocs about
that potential.
-Adrian
--- On Sat, 2/13/10, Adrian Crum wrote:
> From: Adrian Crum
> Subject: Re: XmlSerializer.java
> To: dev@ofbiz.apache.org
> Date: Saturday, February 13, 2010, 11:08 PM
> Actually, this
ead of the current
implementation.
-Adrian
--- On Sat, 2/13/10, Adrian Crum wrote:
> From: Adrian Crum
> Subject: Re: XmlSerializer.java
> To: dev@ofbiz.apache.org
> Date: Saturday, February 13, 2010, 8:01 PM
> I agree. That's exactly what I did in
> my local copy. :-)
&
I agree. That's exactly what I did in my local copy. :-)
-Adrian
--- On Sat, 2/13/10, David E Jones wrote:
> From: David E Jones
> Subject: Re: XmlSerializer.java
> To: dev@ofbiz.apache.org
> Date: Saturday, February 13, 2010, 7:58 PM
>
> We should at least keep t
We should at least keep the deserialization code around forever for backward
compatibility. You can select which deserializer to use based on the root
element or something, that shouldn't be tough.
-David
On Feb 13, 2010, at 8:53 PM, Adrian Crum wrote:
> I recently added the XStream library
I recently added the XStream library to the project - which enables
serializing/deserializing Java objects to XML or JSON.
With that addition, the XmlSerializer class is no longer needed. The XStream
library is more sophisticated and extensible than the home-grown code.
Switching XML serializer
