ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] [Commented] (AXIOM-398) Return value of OMNamedInformationItem#getNamespace() should be normalized
Date Sat, 29 Dec 2012 21:58:12 GMT


Hudson commented on AXIOM-398:

Integrated in ws-axiom-trunk #1305 (See [])
    Code simplification / dead code elimination (OMElement#getNamespace never returns a non
null OMNamespace with an empty namespace URI; see AXIOM-398). (Revision 1426820)

     Result = SUCCESS
veithen : 
Files : 
* /webservices/commons/trunk/modules/axiom/modules/axiom-common-impl/src/main/java/org/apache/axiom/om/impl/common/

> Return value of OMNamedInformationItem#getNamespace() should be normalized
> --------------------------------------------------------------------------
>                 Key: AXIOM-398
>                 URL:
>             Project: Axiom
>          Issue Type: Bug
>          Components: API
>    Affects Versions: 1.2.12
>            Reporter: Andreas Veithen
>            Assignee: Andreas Veithen
>            Priority: Minor
>             Fix For: 1.2.13
> For elements and attributes without namespace, getNamespace() may return two different
values: null or an OMNamespace instance that has both prefix and namespaceURI properties set
to the empty string. The value that is actually returned in this case depends in subtle ways
on how the information item was created. This can be illustrated by the following code snippet:
> OMElement element1 = AXIOMUtil.stringToOM("<root/>");
> System.out.println(element1.getNamespace());
> OMElement element2 = AXIOMUtil.stringToOM("<root xmlns=''/>");
> System.out.println(element2.getNamespace());
> The output is:
> null
> One can see that although the two elements are equivalent, the return value of getNamespace()
is different.
> The return value of getNamespace() should be normalized such that it is always the same
(i.e. null) for information items without namespace.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message