axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeroen van Bemmel (JIRA)" <>
Subject [jira] Commented: (AXIS-1757) AXIS XML interface does not conform to expected DOM behavior
Date Wed, 09 Feb 2005 11:02:12 GMT
     [ ]
Jeroen van Bemmel commented on AXIS-1757:


It may be that the WSS4J code that makes this call using 'null' is not conforming to DOM3,
I am not sure. In any case, wouldn't it be an idea to add

if (ns==null) ns="";

to the code, and keep the rest of the processing as is? People using 'null' should perhaps
have used "" instead, since that is probably what they intended, but adding this will forgive
them for it


> 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