You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commons-dev@ws.apache.org by "Eran Chinthaka (JIRA)" <ji...@apache.org> on 2006/09/13 20:28:22 UTC
[jira] Created: (WSCOMMONS-96) Handling of completeness in OMNodes
is not correct/complete
Handling of completeness in OMNodes is not correct/complete
-----------------------------------------------------------
Key: WSCOMMONS-96
URL: http://issues.apache.org/jira/browse/WSCOMMONS-96
Project: WS-Commons
Issue Type: Bug
Components: AXIOM
Reporter: Eran Chinthaka
Assigned To: Eran Chinthaka
Priority: Blocker
When we add a non-built OMElement to an already built OMElement, the already built OMElement's complete status should be changed to "not completed". And once all the children are completed then parent should be updated with that information as well.
Current code lags proper handling of complete status, which seems to be a bottleneck in handling an OMTree which has multiple non-built elements in different places.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org
[jira] Resolved: (WSCOMMONS-96) Handling of completeness in OMNodes
is not correct/complete
Posted by "Eran Chinthaka (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/WSCOMMONS-96?page=all ]
Eran Chinthaka resolved WSCOMMONS-96.
-------------------------------------
Resolution: Fixed
Fixed in r443065. Thanks Ruchith and Thilina for the help !!
> Handling of completeness in OMNodes is not correct/complete
> -----------------------------------------------------------
>
> Key: WSCOMMONS-96
> URL: http://issues.apache.org/jira/browse/WSCOMMONS-96
> Project: WS-Commons
> Issue Type: Bug
> Components: AXIOM
> Reporter: Eran Chinthaka
> Assigned To: Eran Chinthaka
> Priority: Blocker
>
> When we add a non-built OMElement to an already built OMElement, the already built OMElement's complete status should be changed to "not completed". And once all the children are completed then parent should be updated with that information as well.
> Current code lags proper handling of complete status, which seems to be a bottleneck in handling an OMTree which has multiple non-built elements in different places.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org