[
https://issues.apache.org/jira/browse/WSCOMMONS-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rich Scheuerle resolved WSCOMMONS-369.
--------------------------------------
Resolution: Fixed
Committed 683960
Kudos to Mike Rheinheimer for debugging this complicated issue.
> Adding an OMSE node should not propogate incomplete setting to ancestors
> ------------------------------------------------------------------------
>
> Key: WSCOMMONS-369
> URL: https://issues.apache.org/jira/browse/WSCOMMONS-369
> Project: WS-Commons
> Issue Type: Bug
> Components: AXIOM
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Background:
> A partially parsed OMNode is incomplete (i.e. isComplete() returns false).
> If an incomplete OMNode child is added to a parent, then the parent is also
> marked as incomplete. The assumption is that the parent and child are
> sharing the same builder/parser.
> Problem:
> OMSourcedElements are different than regular OMNodes. They are
> self-contained and sourced by their own independent OMDataSource (which
> provides an independent parser). If an incomplete OMSE child is added to a
> parent, the parent should NOT be marked as incomplete.
> Currently the parent is marked as incomplete, this leads to an unstable OM
> and spurious errors.
> Solution:
> This is a simple change to the OMElementImpl.addChild method.
> I also have a small verification test to validate the change. I will add
> the new code and test later today.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
