[
https://issues.apache.org/jira/browse/AXIOM-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15300135#comment-15300135
]
Boris Dushanov commented on AXIOM-483:
--------------------------------------
Axis2 contains unpredictable number of code invocations that relies on the
1.2.x behavior.E.g.
https://svn.apache.org/repos/asf/axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/deployment/util/Utils.java
(line 1276)
That means that the following PolicyAttachment snippet won't work with 1.3.x as
the 'policy-subject' element is in 'wsp' namespace but is searched by its local
part only:
<wsp:PolicyAttachment xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy";>
<wsp:AppliesTo>
<wsp:policy-subject identifier="binding:soap" />
<wsp:policy-subject identifier="binding:soap12" />
</wsp:AppliesTo>
> 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]
