You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org> on 2005/02/08 13:07:12 UTC
[jira] Commented: (AXIS-1757) AXIS XML interface does not conform to expected DOM behavior
[ http://issues.apache.org/jira/browse/AXIS-1757?page=comments#action_58753 ]
Davanum Srinivas commented on AXIS-1757:
----------------------------------------
Ashu,
please attach your junit test case as well.
-- dims
> 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