Re: Recent change to UtilXml.java breaks talking to jax-ws.

[Adrian Crum <ad...@yahoo.com>]

What we really need to do is make UtilXML support namespaces by providing methods that accept a namespace argument. Then client code that uses namespaces should be updated to use the namespace-aware methods.

-Adrian

--- On Fri, 9/10/10, Jeremiah Christensen <je...@paceap.com> wrote:
> Hello,
> 
> The recent change to UtilXml has caused me to be unable to
> use exported services using jax-ws. The issue is that jax-ws
> adds namespace prefixes to the element names. getNodeName
> returns the element name with the prefix; whereas,
> getLocalName returns just the element name. So, getNodeName
> fails for me when it's being compared to a string like
> "map-Key". 
> 
> Perhaps instead of replacing getLocalName with getNodeName,
> ofbiz could 'or' them, looking for the possibility of both?
> After implementing this locally, I am back in business. See
> attached patch.
> 
> The change to UtilXml.java mentioned above (from ViewSVN):
> <snip>
> Revision 995384 - (view) (download) (annotate) - [select
> for diffs] 
> Modified Thu Sep 9 11:32:28 2010 UTC (31 hours, 44 minutes
> ago) by ashish 
> File length: 47184 byte(s) 
> Diff to previous 995202 (colored)
> Fixing bug of reading node name. When we read first child
> element of the response of any third party integration for
> example ups etc, node name can't be read using
> "node.getLocalName()". So changing  node.getLocalName()
> --> node.getNodeName(). 
> 
> Thanks Vivek for the contribution. 
> </snip>
> 
> Best Regards,
> 
> Jeremiah Christensen
> Web Services Engineer
> PACE Anti-Piracy, Inc.
> 
> 
>