On 01/18/2014 06:36 PM, Jörg Schaible wrote:
Hi Jörg,
thanks for taking the time.
> I am not sure, what you really want to do. The DataHolder that is used
> by default is created for every call to marshal/unmarshal so that the
> converters may communicate within one (un)marshalling process.
here's what i intend to do:
while marshalling my root object i record some information that is not
to be written into the xstream writer.
while unmarshalling, i'd like to pass this recorded information into the
unmarshalling process, so that my converter (that previously had
collected the information) can now reconstruct the full object state
that is more than what can be found in the reader.
my usecase is something like:
- marshalling an object to xml and excluding blob data.
- moving detached blob-data and marshalled object over the wire
- unmarshalling and re-attaching the blob data.
it works nicely with calling mashall/unmarshall myself, providing a
custom DataHolder.
the only inconvenience is, that - calling unmarshall - i need to know
what the root-type is. not that much of a problem, i'd just wanted to
mention it.
my misconception was newDataHolder being a factory method that provides
a hook to tweak the object used by xstream.
thanks, uwe
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
