Re: Ozone Collection class serialization

On Tue, 2004-11-23 at 08:28, Philip C C wrote:

(snip)

> Are these the expected behaviour for FullTreeMap,
> NodeTreeMap and normal ozone object with Private
> access right?

I am afraid that there _is_ no 'expected behaviour'; an ozone backend
storage (wizardStore is currently the only one) is free to
serialize/save or deserialize/read whichever ozone compatible objects at
whatever time it pleases. Trying to understand (or heaven forbit: build
code based on) when or where objects are serialized is like trying to
understand the specifics of a JVM garbage collector.

> Why update a FullTreeMap does not affect NodeTreeMap
> but by updating NodeTreeMap will cause all the
> elements in 
> FullTreeMap got serialized?

Why does it matter?

> And why update an attribute in normal ozone object,
> will cause all the elements in FullTreeMap got
> serialized but 
> not to NodeTreeMap?

Again: why do you need to know? I can probably create a test case that
does not conform to your findings. I take it knowing what and where
serialization takes place is just a _means_ to reach a goal; what _goal_
do you want to reach?

Cheers,
Leo

-- 
Leo Mekenkamp; phone: +31 641234919
Care about freedom and innovation? http://openoffice.org,
http://ozone-db.org, http://mozilla.org, http://linux.org



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/