Hi Ajith,
Is there a particular reason you want to only implement the
XMLStreamWriter output? The OMDataSource provides a choice of output
methods for compatibility with Axiom's supported output methods. If you
limit your interface to doing XMLStreamWriter only, isn't that going to
break code that uses the other output techniques?
- Dennis
Ajith Ranabahu wrote:
Hi All,
There have been some talk about performance improvements for Axis2
next steps. So here is a small proposal of how to do a possible
optimization with AXIOM and ADB.
1. AXIOM needs to have an interface that allows a XMLStreamWriter to
passed. This allows the implementer (of the interface) to have code
that directly uses the writer. (Currently the OMDataSource has the
necessary methods. We actually need only one, the write method).
2. We have a special OMElement abstract class that implements the
OMDataSource that has a constructor taking in an ADBBean.
3. All ADB beans are added an extra method to pump out a special
OMElement that have the write code generated. Note that this is a
concrete class based on the special OMElement mentioned in [2].
4. The ADB databinding template is changed to get the OMElement from
the ADBBean instead of building one. We basically change the
implementation of the toOM method.
Thoughts ?
BTW - I am still writing the answer to Dennis about unwrapping :)
--
Ajith Ranabahu
p.s. - sorry for resending. Messed up the subject in the first one :(
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
