ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AXIOM-483) OMElementImpl.getChildrenWithName() is too restrictive and not compatible with 1.2.x
Date Sat, 04 Jun 2016 17:01:59 GMT

    [ https://issues.apache.org/jira/browse/AXIOM-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15315571#comment-15315571
] 

Andreas Veithen commented on AXIOM-483:
---------------------------------------

The WS-Policy Attachment spec recommends that unrecognized child elements of wsp:AppliesTo
should be ignored. Therefore I think the correct solution is to actually do exactly that,
and in addition emit a warning message so that users can easily identify policies that are
interpreted in an incorrect way in Axis2 1.7.x. Please create a JIRA ticket in the AXIS2 project
for that.

> 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: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org


Mime
View raw message