axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jongjin Choi (JIRA)" <>
Subject [jira] Commented: (AXIS-1757) AXIS XML interface does not conform to expected DOM behavior
Date Thu, 10 Feb 2005 08:06:15 GMT
     [ ]
Jongjin Choi commented on AXIS-1757:

This issue is addressed in 'Backward Compatibility' section of Xerces-J home page and DOM
Level 2 errata. (

According to that, I think, it is legal that the user specify null instead of "" as first
parameter of getAttributeNS and the result should be same in both case.
I think that the patch is reasonable.

> AXIS XML interface does not conform to expected DOM behavior
> ------------------------------------------------------------
>          Key: AXIS-1757
>          URL:
>      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/
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:
If you want more information on JIRA, or have a bug to report see:

View raw message