Hi Oshani, This is great and +1 for AXOIM taking care of the StAX parsing. Its the right thing to do. I have a few questions, please find them inline.
On 6/20/06, Oshani Seneviratne <[EMAIL PROTECTED]> wrote:
Hi, Chinthaka, thank you very much for the advice and the explanation on AXIOM & StAX. I am using the 2nd option, where the the AXIOM object model is built from the WSDL and the Woden interface implemented from it.
I presume you are talking about the Element model interfaces here. So give me a little isight here. Are you gonna have another implementation of element model interfaces?? like AXIOMBasedDescriptionImpl implements Description, DescriptionElement AXIOMBasedBindingImpl implements Description, DescriptionElement , etc. What of the Component. How can i get the component model build using a StAX parser?? Are you gonna implement the toComponent method as well. FYI Axis2 depends on the flattening capability of the component model. Is this the right picture or did i misinterpreted what you said.
My idea is to have an OMWSDLReader which does not have any DOM dependencies and uses AXIOM to get whatever the elements in the WSDL and parse them into the Woden specific objects. This approach is quite easy, and the current implementation in Woden seem to support it. However, when I was trying to handle the extension elements and attributes, I came across several classes such as ExtensionDeserializer, XMLAttrImpl (and in fact a whole bunch of *AttrImpl classes) which seem to be heavily dependent on DOM. Can somebody please explain whether it's possible to work around these classes? Or would it be possible for the init and convert methods to take in OMElements? I really couldn't grok the logic behind handling the extension attributes and elements in Woden. So, any insight on this too would be greatly appreciated. Thanks and Regards, Oshani. On 6/20/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote: [snip] > There can be two ways to implement this. > > 1. To implement Woden object model extending Axiom elements. This is > what I did to implement SOAP on top of Axiom (Axiom is a pure XML info > set representation). > > 2. Build the Axiom object model from the parser and to use that to > populate the Woden model. > > First approach is preferred as it won't create two object models. But > this requires some one to re-implement Woden object model. > So the best short term option is to go for the second option, IMO. > > -- Chinthaka --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Chathura Herath http://people.apache.org/~chathura/ http://chathurah.blogspot.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
