[
https://issues.apache.org/jira/browse/COLLECTIONS-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Neidhart updated COLLECTIONS-446:
----------------------------------------
Attachment: COLLECTIONS-446.patch
I think this makes sense.
Please find attached a first patch with the following idea:
Create an EquatorWrapper that wraps the actual object and delegates
equals/hashCode to the Equator.
The isEqualCollection method creates a transformed collection (O ->
EquatorWrapper<O>) for each of the two input collections and passes it on to
the already existing isEqualCollection(Collection, Collection).
A simple test attached:
* compare two integer lists
* equator: looks for odd/even numbers
Missing javadoc and more tests.
> Overload CollectionUtils.isEqualCollection to accept an Equator instance
> ------------------------------------------------------------------------
>
> Key: COLLECTIONS-446
> URL: https://issues.apache.org/jira/browse/COLLECTIONS-446
> Project: Commons Collections
> Issue Type: Improvement
> Components: Collection
> Affects Versions: 4.0
> Reporter: Matt Lachman
> Priority: Minor
> Attachments: COLLECTIONS-446.patch
>
>
> As of COLLECTIONS-242, a new Equator interface has been added to the API. It
> would be nice to take advantage of that when comparing collections so it can
> be done on something other than {{Object.equals(Object other)}}. I propose a
> new method signature as below:
> {code:java}
> public static boolean isEqualCollection(Collection a, Collection b, Equator e)
> {code}
> Related to this is my post on StackOverflow:
> [http://stackoverflow.com/questions/15094818/compare-two-java-collections-using-comparator-instead-of-equals]
--
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
