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

Hudson commented on AXIOM-172:
------------------------------

Integrated in ws-axiom-trunk #667 (See 
[https://builds.apache.org/job/ws-axiom-trunk/667/])
    * Removed the old test cases for AXIOM-78 which failed to provide evidence 
for the issue.
* Added a regression test for AXIOM-78 and AXIOM-172.

veithen : 
Files : 
* 
/webservices/commons/trunk/modules/axiom/modules/axiom-tests/src/test/java/org/apache/axiom/om/IteratorTest.java
* 
/webservices/commons/trunk/modules/axiom/modules/axiom-testsuite/src/main/java/org/apache/axiom/ts/OMTestSuiteBuilder.java
* 
/webservices/commons/trunk/modules/axiom/modules/axiom-testsuite/src/main/java/org/apache/axiom/ts/om/element/TestGetChildrenWithNameNextWithoutHasNext.java

                
> OMChildrenQNameIterator doesn't work correctly if hasNext() is not called 
> before next()
> ---------------------------------------------------------------------------------------
>
>                 Key: AXIOM-172
>                 URL: https://issues.apache.org/jira/browse/AXIOM-172
>             Project: Axiom
>          Issue Type: Bug
>          Components: DOOM, LLOM
>    Affects Versions: 1.2.8
>            Reporter: Andreas Veithen
>            Assignee: Andreas Veithen
>            Priority: Minor
>             Fix For: 1.2.11
>
>
> OMChildrenQNameIterator only works correctly if hasNext() is called before 
> each invocation of next(). While this is usually the case, it is not at all 
> required!

--
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]

Reply via email to