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

Hudson commented on AXIOM-365:
------------------------------

Integrated in ws-axiom-trunk #405 (See 
[https://builds.apache.org/job/ws-axiom-trunk/405/])
    AXIOM-365:
* Modified the iterator implementation so that a 
ConcurrentModificationException is thrown if the current node is removed using 
a method other than Iterator#remove().
* Fixed two instances where Axiom itself uses iterators in an incorrect way.

veithen : 
Files : 
* 
/webservices/commons/trunk/modules/axiom/modules/axiom-api/src/main/java/org/apache/axiom/om/impl/traverse/OMAbstractIterator.java
* 
/webservices/commons/trunk/modules/axiom/modules/axiom-impl/src/main/java/org/apache/axiom/om/impl/llom/OMSourcedElementImpl.java
* 
/webservices/commons/trunk/modules/axiom/modules/axiom-dom/src/main/java/org/apache/axiom/om/impl/dom/ParentNode.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/TestGetChildrenConcurrentModification.java


> Add ConcurrentModificationException support to iterators
> --------------------------------------------------------
>
>                 Key: AXIOM-365
>                 URL: https://issues.apache.org/jira/browse/AXIOM-365
>             Project: Axiom
>          Issue Type: Improvement
>    Affects Versions: 1.2.11
>            Reporter: Andreas Veithen
>            Assignee: Andreas Veithen
>             Fix For: 1.2.12
>
>
> As explained in the user guide [1], the behavior of iterators returned by 
> methods such as OMContainer#getChildren() slightly changed in Axiom 1.2.10 
> (see AXIOM-333). This may cause subtle issues (such as AXIS2-5071) which are 
> difficult to detect. The Iterator implementations should be improved such 
> that a ConcurrentModificationException is thrown if the current node is 
> removed, exactly as the iterators of the Java 2 collection framework 
> (java.util) do.
> [1] http://ws.apache.org/axiom/userguide/ch04.html#iterator-changes

--
This message is automatically generated by JIRA.
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