Hi Bill,
Bill Schoolfield wrote:
>> Actually I don't think that you can read or write the first version with
>>> XStream at all. XStream will always escape those two characters in a
>>> String and unescape them at deserialization
>
> Jorg,
>
> Yes, it does escape these characters. No it does not unescape them
> at deserialization.
>
> The "item" member in my created object has the escaped text, not the
> original text.
Hard to believe ;-)
> Maybe this is a bug.
This is just a so essential functionality. How do you initialize XStream? Is
the "item" written by XStream's converters or do you use an own one?
Cheers,
Jörg
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
