First of all, I'm extremely sorry for not being able to reply to the two email threads regarding woden serialization. I was a bit busy with another very critical project and couldn't concentrate on Woden that much during the past few weeks.
Anyway, here's my two cents worth.
On 10/18/06, Eran Chinthaka <
[EMAIL PROTECTED]> wrote:
We DO build the OM tree inside woden, but it is only at the parsing level. It is not visible to the Woden Element API.
You asked "... isn't it just a matter getting the OMElement and serializing it, if I use OM Reader?"
Well, I suppose if we have the DescriptionElement extending from OMElement, it is threoretically possible. Although this is doable (of course for the AXIOM implementation only), it would lead to lot of API changes!
Any comments/suggestions?
I really couldn't look that deep into the direct requirement as of now. But from the discussion in the previous thread and this one, I guess the most viable solution is to implement a WSDLWriter.
Since Axis2 requires this a lot, let's make it a priority for M8. As soon as I finish the work on OMXMLElement and refactorings in OMWSDLReader, I would like to contribute.
Thanks and Regards,
Oshani
Lawrence Mandel wrote:
>
> Chinthaka,
>
> Thanks for the info about why Axis2 needs Woden serialization. You
> mentioned in a previous post that you may get this for free with Axiom.
Nope, the way I thought was wrong. I assumed we keep the build OM tree
inside Woden, but seems it is not the case.
We DO build the OM tree inside woden, but it is only at the parsing level. It is not visible to the Woden Element API.
You asked "... isn't it just a matter getting the OMElement and serializing it, if I use OM Reader?"
Well, I suppose if we have the DescriptionElement extending from OMElement, it is threoretically possible. Although this is doable (of course for the AXIOM implementation only), it would lead to lot of API changes!
Any comments/suggestions?
> If that's the case we can defer support in Woden until after the next
> W3C interop event. Has anyone (Oshani) looked into this and will this
> allow Axis2 to move forward past this critical requirement?
I think there should be a serializer for Woden. At least from Axis2 POV,
this is important, but I don't wanna mess up with your schedules. Can we
please add a JIRA for this?
I really couldn't look that deep into the direct requirement as of now. But from the discussion in the previous thread and this one, I guess the most viable solution is to implement a WSDLWriter.
Since Axis2 requires this a lot, let's make it a priority for M8. As soon as I finish the work on OMXMLElement and refactorings in OMWSDLReader, I would like to contribute.
Thanks and Regards,
Oshani
