[ http://issues.apache.org/jira/browse/AXIS-1757?page=comments#action_58802 ] Ashutosh Shahi commented on AXIS-1757: --------------------------------------
OK, my patch was considering that if namespaceURI is null, we take it as null; but from what i see in axis code, it is taken as empty string "". So this patch can be considered invalid. But is this a correct thing to do? Users if not aware, will do a getAttributeNS call using null, as Jeroen did, and will not get the expected output. However if they give "" instead of null output is correct. Ashutosh > AXIS XML interface does not conform to expected DOM behavior > ------------------------------------------------------------ > > Key: AXIS-1757 > URL: http://issues.apache.org/jira/browse/AXIS-1757 > Project: Axis > Type: Bug > Components: Basic Architecture > Versions: 1.2 > Environment: all platforms (mine is Windows 2000/XP), JDK 1.4.2_06 > Reporter: Jeroen van Bemmel > Attachments: bug-1757.txt > > The AXIS implementation of some DOM interfaces (in particular: > ws-axis/java/src/org/apache/axis/message/MessageElement.java method > getAttributeNS) does not behave as expected for DOM. In one case this caused > a WSS4J getCanonicalizerMethod() to fail (don't remember the exact signature > or file), since it uses 'null' as a first parameter (namespace). > As can be seen in Xerces-J NamedNodeMapImpl (method protected int > findNamePoint(String namespaceURI, String name) ) a first parameter of 'null' > should skip a check on namespace, and simply return any node with a matching > localname or nodename. > Since MessageElement implements SOAPElement which extends Element, one would > expect the behavior to conform. Or am I missing something here? > JvB -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
