[Axis2] OM - pre-chat discussion on Chat Topics

[Eran Chinthaka <ch...@opensource.lk>]

 

Hi all, 

 

I saw some chat topics to be discussed in the next topic. Since we have only
limited time, I thought of pre-discussing them in the mailing list.

 

1.     JDK 1.4 compatibility (any particular verions of 1.4.x?) 

Current implementations were based on JDK 1.4.2. But I think these can be
run on any jdk 1.4.x version as required by the Axis 2 Summit

2.     how to access stream for SOAP : Body? API? 

Thought of exposing the stream through the StAX parser directly. One can get
a reference to the StAX parser from OM or he can access the StAX by the StAX
event generator provided by OM. Here one has the option of either switching
on or off caching.

Here if you take current use cases, Security handler will be accessing the
body, at most, before the provider. For security, a DOM Wrapper will be
given. And for the Provider, he can either access the StAX parser directly
or can go through OM.

In the linked list implementation, one has the facility getting StAX events,
starting from any given location, irrespective of parser has already parsed
that part or not. 

(Currently Linked List supports XPP only, but will be changed to Typed StAX
soon.)

a.             how to support flexibly multiple APIs (DOM, SAAJ, ...) even
those that we currently do not know about ... 

>From the current OM API, one has the access to total infoset. Almost nothing
in the infoset is lost. We can easily wrap the OM API from any other API
like DOM, JDOM, SAAJ or any other we do not know.

b.             related: efficient support of different binding techniques:
SAX stream, StAX stream,  <http://wiki.apache.org/ws/XmlBeans> XmlBeans,
Castor, JAXB, ... 

I think we discussed a bit about this earlier through the mailing list.
Since there are no data binding tools directly supporting StAX, we thought
of writing a StAX --> SAX converter, where any databinding tool can be
plugged in.

c.              should we add more setters/getters methods? make it more
JDOM-like? 

I think this is achieved more practically to some extent, by incorporating a
SAAJ like API to OM. This can be found in
http://svn.apache.org/repos/asf/webservices/axis/trunk/java/dev/scratch/chin
thaka/OM API

d.             how to wrap OMEleemnt with DOM Element? 

This is being addressed in 2a above

e.             should we allow String as element content beside OMText to
allow very lightweight XML trees 

This is a good idea. Any idea of integrating this to the existing
implementations .... ???

 

Thoughts & Comments ........ ???

 

  _____  

Eran Chinthaka

Lanka Software Foundation