[
https://issues.apache.org/jira/browse/AXIOM-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13284372#comment-13284372
]
Hudson commented on AXIOM-385:
------------------------------
Integrated in ws-axiom-trunk #994 (See
[https://builds.apache.org/job/ws-axiom-trunk/994/])
AXIOM-385: Removed code that is either redundant or that is no longer
reachable through the API (because DocumentImpl no longer implements OMNode).
(Revision 1343196)
Result = SUCCESS
veithen :
Files :
*
/webservices/commons/trunk/modules/axiom/modules/axiom-dom/src/main/java/org/apache/axiom/om/impl/dom/ChildNode.java
*
/webservices/commons/trunk/modules/axiom/modules/axiom-dom/src/main/java/org/apache/axiom/om/impl/dom/DocumentImpl.java
> DOOM class hierarchy is inconsistent with the Axiom interface hierarchy
> -----------------------------------------------------------------------
>
> Key: AXIOM-385
> URL: https://issues.apache.org/jira/browse/AXIOM-385
> Project: Axiom
> Issue Type: Bug
> Components: DOOM
> Affects Versions: 1.2.12
> Reporter: Andreas Veithen
> Assignee: Andreas Veithen
> Fix For: 1.2.13
>
>
> The OMDocument interface extends OMContainer, but not OMNode. On the other
> hand, DocumentImpl implements both OMDocument and OMNode (because it extends
> NodeImpl which implements OMNode).
> That causes problems with code such as this (which is perfectly consistent
> with the Axiom API and which works correctly with the LLOM implementation):
> if (item instanceof OMNode) {
> ...
> OMContainer parent = ((OMNode)item).getParent();
> ...
> }
--
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]
