[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ws-general
Subject:    [jira] [Commented] (AXIOM-483) OMElementImpl.getChildrenWithName() is too restrictive and not compat
From:       "Boris Dushanov (JIRA)" <jira () apache ! org>
Date:       2016-05-30 10:22:12
Message-ID: JIRA.12971500.1463742814000.330830.1464603732828 () Atlassian ! JIRA
[Download RAW message or body]


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

Boris Dushanov commented on AXIOM-483:
--------------------------------------

Yes, your understanding is correct but why is that acceptable? Finding and changing \
an unknown number of policies might not be trivial at all. It will also harden the \
upgrade to Axis 1.8.0. I agree that Axiom 1.3.x behavior is correct now but I'm not \
sure that users should suffer from that.Do you see a different approach?

> 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


[prev in list] [next in list] [prev in thread] [next in thread]