[
https://issues.apache.org/jira/browse/AXIOM-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299969#comment-15299969
]
Andreas Veithen commented on AXIOM-483:
---------------------------------------
bq. In other words, passing an empty namespace is interpreted as a wildcard
i.e. any namespace. That's not the case in 1.3.x. Is that intentionally done?
Yes, because this is undocumented legacy behavior.
> OMElementImpl.getChildrenWithName() is too restrictive and not compatible
> with 1.2.x
> ------------------------------------------------------------------------------------
>
> Key: AXIOM-483
> URL: https://issues.apache.org/jira/browse/AXIOM-483
> Project: Axiom
> Issue Type: Bug
> Components: LLOM
> Affects Versions: 1.3.0
> Reporter: Boris Dushanov
> Priority: Critical
> Fix For: 1.3.0
>
>
> In 1.2.x org.apache.axiom.om.impl.llom.OMElementImpl.getChildrenWithName()
> contains the following comment:
> // The getChidrenWithName method used to tolerate an empty namespace
> // and interpret that as getting any element that matched the local
> // name. There are custmers of axiom that have hard-coded
> dependencies
> // on this semantic.
> // The following code falls back to this legacy behavior only if
> // (a) elementQName has no namespace, (b) the new iterator finds no
> elements
> // and (c) there are children.
> This seems to be not the case in 1.3.0 and the method is now restrictive.The
> current behavior is correct but the problem is that it's not backward
> compatible and will lead to many issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
