axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eran Chinthaka" <>
Subject RE: [Axis2]OM structure
Date Tue, 28 Dec 2004 05:34:36 GMT

>>Hi all,
>>If you look at the code now, the OMAttribute and the OMNamespace are
>>both detached from the node hierarchy and are standalone now. I
>>suppose the point is to make them immutable. However this has opend up
>>some problamatic areas in the implementation.
>>1. We can no longer use the link lists to store the attributes or the
>>namespaces. This causes the implementations to use collection classes
>>(standard or custom) which may increase the memory usage. This is
>>exactly what we tried to avoid.

 [Chinthaka] I had no option but to introduce collection classes to store
attributes and namespaces, as we detach them from Node Structure. And I
think that we have to do.

>>2. We still haven't implemented the namespace and attribute
>>declaration order. Link list will be a very convenient way to do that.
>>But since attributes and namespaces are not nodes we cannot do that.

 [Chinthaka] This I will implement, after M1.

>>I am absolutely -1 for making the changes right now 

[Chinthaka] me too.

-- Eran Chinthaka

(in time for M1)
>>but I guess we should at least decide on what kind of structure our OM
>>should have.
>>thoughts ?
>>Ajith Ranabahu

View raw message