I'm not really sure what you meant by a typed axiom. Did you mean to generate special OMElements that encapsualte integer (and other type) content directly ?
Ajith
How about doing Typed STAX and a Typed AXIOM?
Its possible that the "Special OMElement" could be used to do this. Basically I want to be able to avoid the cost of converting from bytes->char->int and just do byte->int. Once we get a decent binary serialization of XML this will improve further, because we could go encoded-int->int.
PaulOn 6/16/06, R J Scheuerle Jr < [EMAIL PROTECTED]> wrote:Ajith,
Sounces like a great idea. I have some questions.
A) Should the "Special OMElement" have a constructor that takes an Object ?
It would be nice if a user could create a derivation of the "Special OMElement" and source it with other (non-ADB) objects.
-----------------------------------------
B) If an OM tree contains a "Special OMElement" as a leaf node and the "Special OMElement" is touched, is the "Special OMElement" converted into a normal OMElement subtree ?
I assume that the following takes place:
i) The "Special OMElement" is touched.
ii) The OM implementation detaches the "Special OMElement" from the tree.
iii) A new OMElement is inserted into the tree at the same location.
iv) The new OMElement is sourced by the XMLStreamReader obtained from the "Special OMElement".
Is this correct ?
-----------------------------------------
C) Assuming that the answer to (B) is true, can the "Special OMElement" represent more than a single sub-tree ?
Suppose the logical content of the "Special OMElement" is the following.
<p:a xmlns:p="urn://sample" />
<p:b xmlns:p="urn://sample" />
Does the above get converted into two peer elements, or is this an erroneous situation ?
-----------------------------------------
Thanks,
Rich Scheuerle
Senior Developer
IBM WebSphere Web Services Engine & Tooling
512-838-5115 (IBM TL 678-5115)
"Ajith Ranabahu" < [EMAIL PROTECTED]>
"Ajith Ranabahu" <[EMAIL PROTECTED]>
06/16/2006 07:37 AM
[email protected]
To
"Axis developer list" <[email protected]>, [email protected]
cc
Subject
[Proposal][Axis2][Axiom] Adding writable capability to OM elements
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]
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
--
Ajith Ranabahu
