Re: [Proposal][Axis2][Axiom] Adding writable capability to OM elements

[Chuck Williams]

This seems like a good idea to me as it is extra work to read the events out of the ADBBean just to turn around and rewrite them.  It's better to write them directly.  I presume this would apply to toEnvelope() as well as to toOM()? Chuck Ajith Ranabahu wrote on 06/16/2006 02:37 AM: 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] -- Chuck Williams Manawiz Principal V: (808)885-8688 C: (415)846-9018 [EMAIL PROTECTED] Skype: manawiz AIM: hawimanawiz Yahoo: jcwxx --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]