[ 
https://issues.apache.org/jira/browse/AXIOM-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Veithen updated AXIOM-387:
----------------------------------

    Fix Version/s: 1.2.14
    
> Deprecate getChildrenWithName and introduce a replacement method
> ----------------------------------------------------------------
>
>                 Key: AXIOM-387
>                 URL: https://issues.apache.org/jira/browse/AXIOM-387
>             Project: Axiom
>          Issue Type: Task
>          Components: API
>            Reporter: Andreas Veithen
>            Priority: Minor
>             Fix For: 1.2.14
>
>
> The behavior of OMElement#getChildrenWithName is somewhat ill defined for 
> QNames without namespace. In earlier Axiom versions, for such QNames, the 
> returned iterator would only match the local name and return child elements 
> with any namespace. This was changed in r522259, but the legacy behavior was 
> later restored by AXIOM-11 to avoid breaking existing code. However, this 
> legacy behavior is only supported by LLOM. DOOM always uses strict QName 
> matching. It should also be noted that none of this is properly documented in 
> the Javadoc of the getChildrenWithName method.
> To enable us to eventually get rid of this legacy code, we should
> (1) deprecate OMElement#getChildrenWithName
> (2) introduce a replacement method (getChildrenWithQName) with a well defined 
> behavior (i.e. that always uses strict QName matching)
> (3) update the documentation to recommend users to migrate to 
> getChildrenWithQName or getChildrenWithLocalName depending on the use case

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to