ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] [Commented] (AXIOM-116) Don't call if builder is completed
Date Sun, 13 Jan 2013 15:36:12 GMT


Hudson commented on AXIOM-116:

Integrated in ws-axiom-trunk #1358 (See [])
    Dead code elimination:

If OMNavigator#isNavigable() and OMNavigator#isCompleted() both return false, then this means
that the next node has not been built. This implies that there must be a builder and that
the builder is not complete, i.e. builder != null and StAXOMBuilder#isCompleted() returns

Note that this code was added in AXIOM-116, but no unit test was ever produced to show the
purpose of this code. (Revision 1432625)

     Result = SUCCESS
veithen : 
Files : 
* /webservices/commons/trunk/modules/axiom/modules/axiom-common-impl/src/main/java/org/apache/axiom/om/impl/common/

> Don't call if builder is completed
> -------------------------------------------------
>                 Key: AXIOM-116
>                 URL:
>             Project: Axiom
>          Issue Type: Bug
>            Reporter: Rich Scheuerle
>            Assignee: Rich Scheuerle
> Problem:
> is invoked with a builder that is completed.  I received the following
stack trace from Huiran Wang.
> Caused by:
>        at
>        at
>        at
>        at
> Analysis:
> This could be a side effect of OMSourcedElement usage.  I don't have a representative
unit test.
> Solution:
> However I am going to add some additional trace and a slight accomodation in the code.
 There are several places
> where it is easy to ask the builder whether it is "complete" prior to calling
> I will be committing a small change soon.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message