Hi Pradeep, Sorry for last mail Gmail was quicker than me....... :)
>> XMLElement >> elem=(UnknownExtensionElement)element.getElement(); >> Element domelement=(Element)elem.getSource(); It's true using this approach you can retrieve Policy extensions as XMLElements . but it is possible to have any other extensions in WSDL documents . as a example <wsdl2:description> <aaa:Ele xmlns:aaa="http://aaa";> </aaa:Ele> <bbb:Ele xmlns:bbb="http://bbb";> </bbb:Ele> <wsp:Policy xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"; > </wsp:Policy> So how you could ensure that your are getting only Policy elements , because getExtensionElements() return all extenstion elements. I know when you call PolicyUtil with wrong XML content it will throw an exception , in that way you could handle this issue or as you mentioned in your last mail you could check for QName. But I feel we need to come up with some smart solutions for public open source projects like Axis2 without going to obvious solutions , to keep it's quality , so better to use extenstion based approach instead of UnknownExtensionElement approach. because it will provide only Policy extensions not any other extensions. and that's what Woden promotes for handling extension as the recommended way. Any way those are my personal thoughts , Let's see whether some one else have any other comments for this . Thanks , On Wed, Mar 25, 2009 at 4:06 PM, Pradeep Fernando <[email protected]> wrote: > Hi sagara , > > Im comparing the Qname against the element type. so i only get policy > elements. > think it is good enough. Isn't it an overkill to implement deserializer when > all you need is DOM element? > WDYT ? > > thanks > Pradeep Fernando. > -- Sagara Gunathunga Blog - http://ssagara.blogspot.com Web - http://sagaras.awardspace.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
