[
https://issues.apache.org/jira/browse/COLLECTIONS-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Vahrst updated COLLECTIONS-322:
--------------------------------------
Attachment: nodelistAsIterable.patch
I implemented the suggested Utility methods, which provide an Iterable for a
given NodeList or ParentNode. See nodelistAsIterable.patch
I chose IteratorUtils as implementation class, I found this class matching best
for the new services.
The util methods now allow easy iteration over org.w3c.NodeLists or ChildNodes
of a given parent node:
{code}
for(Node childNode : IteratorUtils.asIterable(parentNode){
... do something;
}
{code}
> Adds a Collections wrapper around the w3c NodeList
> --------------------------------------------------
>
> Key: COLLECTIONS-322
> URL: https://issues.apache.org/jira/browse/COLLECTIONS-322
> Project: Commons Collections
> Issue Type: Improvement
> Components: List
> Reporter: Hasan Diwan
> Priority: Minor
> Fix For: 4.0
>
> Attachments: NodeListAsCollection.java, nodelistAsIterable.patch,
> patch.txt, TestNodeListAsCollection.java
>
>
> org.w3c.dom.NodeList is defined as an "abstract collection of Nodes" and
> java.util.List is defined as "An ordered collection (also known as a
> sequence). The user of this interface has precise control over where in the
> list each element is inserted. The user can access elements by their integer
> index (position in the list), and search for elements in the list.". It
> seemed similar enough, so I did an implementation of the useful methods,
> while throwing the appropriate exception when the method wouldn't make sense.
--
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: http://www.atlassian.com/software/jira
