Re: Ozone Collection class serialization

Hi, 
Thanks for the replay..I have few doubts ...please
replay.

I am creating one NodeTreeMap collection class (A)
with OzoneInterface.Private access right, one
FullTreeMap 
Collection class (B) with OzoneInterface.Private
access right and 
one OzoneObject class (C) with OzoneInterface.Private
access right inside a class 
as its three attributes.

I noticed that whenever a new element (element is a
serializable object which extends Serializable) is
added 
to collection A, elements in collection A and B and
also object C got serialized
(the writeObject() method is called).

If a new element is added to collection B, elements in
collection A are not serialized, only 
elements in collection B and object C got serialized.

If a update method in object C is called, elements in
collection A are not serialized, only
elements in collection B and object C got serialized.


Are these the expected behaviour for FullTreeMap,
NodeTreeMap and normal ozone object with Private
access right?
Why update a FullTreeMap does not affect NodeTreeMap
but by updating NodeTreeMap will cause all the
elements in 
FullTreeMap got serialized?
And why update an attribute in normal ozone object,
will cause all the elements in FullTreeMap got
serialized but 
not to NodeTreeMap?

But I see the collection classes behave differently
when the elemets in the lists are Ozone Objects
itself.

--- Wieslaw Faruga <[email protected]> wrote:

> On 21 Nov 2004 at 22:48, Philip C C wrote:
> 
> Please read again what has written Leo.
> The ozone objects are written in groups. If you are
> adding a new elements to two 
> separated ozone collections, these objects may be
> added to a single cluster and then 
> will be written together. The currently used
> "WizardStore" storage system creates a 
> new cluster (a file objects container) only in a
> following cases:
> 1. a new ozone object is created by different user.
> 2. the cluster size is greater than 64K.
> 
> Cheers,
> Wieslaw
> 
> > Hi,
> > Now I am using two NodeTreeMapImpl collection
> class
> > (say collection A and B) inside a class as its two
> > attributes. Now I noticed that whenever collection
> A
> > get updated (added a new element to the
> collection),
> > elements in collection B got serialized (get
> called
> > wrireObject method). I don't want collection B to
> get
> > updated/affected when I am updating collection A. 
>  
> > Pls replay..
> > 
> > Thanks,
> > Philip C C
> > 



		
__________________________________ 
Do you Yahoo!? 
Meet the all-new My Yahoo! - Try it today! 
http://my.yahoo.com 
 



-------------------------------------------------------
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/