[AXIOM-365] Add ConcurrentModificationException support to iterators

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.11
• Fix Version/s: 1.2.12
• Assignee: Andreas Veithen
• Reporter: Andreas Veithen
• Created: 10/Jun/11 18:40
• Updated: 07/Jul/11 19:19
• Resolved: 10/Jun/11 19:26

Description

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

Issue Links

• is related to: AXIS2-5071 Failure to populate all members of an xs:sequence in a SOAP header