[wsf-c-dev] AXIOM NG

[Samisa Abeysinghe]

James Clark wrote:
> On Fri, 2006-12-08 at 20:18 +0700, James Clark wrote:
>   
>> Here's my thinking about how XML might be handled in a future version of
>> the SOAP stack.
>>     
>
> I forgot to ask one question. Suppose we implemented an AXIOM NG along
> the lines of what I suggested. How hard would it be to adapt the rest of
> the code base to use this?
>   
IMHO, it would not be that hard as long as we can figure out how to map 
the current OM tree traversal mechanisms to the semantics in the new model.
Just to give an indication on how we use AXIOM now, 
AXIOM_NODE_GET_DATA_ELEMENT is the most frequently used call. The next 
in line in terms of frequency are AXIOM_NODE_GET_FIRST_CHILD, 
AXIOM_NODE_ADD_CHILD, AXIOM_NODE_GET_NODE_TYPE, AXIOM_NODE_TO_STRING and 
AXIOM_NODE_SERIALIZE.

 There are two main uses of AXIOM in the current Axis2/C engine:
    1. Parse config files
    2. Process SOAP messages
For case one, USE_ONCE would almost always work, as we just need to pick 
parameters and then forget about OM. There could be very few cases where 
we would want keep the stuff in AXIOM format (Kaushalye, do we do that 
for security parameters?)

For case two, most of the SOAP headers would be use once, e.g. in 
addressing, we fill in message information based on the headers 
available, and then forget about AXIOM representation. However, SOAP 
body would be USE_MANY most of the time.

Samisa...