[
https://issues.apache.org/jira/browse/AXIOM-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053022#comment-13053022
]
Ivan commented on AXIOM-365:
----------------------------
This change brought an issue while using SOAPHeader.extractAllHeaderElementsd
method, a ConcurrentModificationException exception is always thrown.
The test code is like :
MessageFactory fac = MessageFactory.newInstance();
SOAPMessage msg = fac.createMessage();
SOAPPart sp = msg.getSOAPPart();
SOAPEnvelope envelope = sp.getEnvelope();
SOAPHeader hdr = envelope.getHeader();
SOAPHeaderElement she1 = hdr.addHeaderElement(envelope.createName("a",
"b", "c"));
Iterator iterator = hdr.extractAllHeaderElements();
> 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]
