Issue Details (XML | Word | Printable)

Key: MULE-3720
Type: Improvement Improvement
Status: Closed Closed
Resolution: Cannot Reproduce
Priority: Major Major
Assignee: Daniel Feist
Reporter: Daniel Feist
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Mule

Implement equals methods for service, component etc.

Created: 25/Sep/08 09:43 PM   Updated: 30/Nov/08 07:00 PM
Component/s: Core: (other)
Affects Version/s: None
Fix Version/s: 2.x Product Backlog

Time Tracking:
Original Estimate: 6 hours
Original Estimate - 6 hours
Remaining Estimate: 2 days
Time Spent - 7 hours Remaining Estimate - 2 days
Time Spent: 7 hours
Time Spent - 7 hours Remaining Estimate - 2 days

Labels:
User impact: Medium


 All   Comments   Work Log   Change History   Transitions   FishEye      Sort Order: Ascending order - Click to sort in descending order
Daniel Feist added a comment - 28/Sep/08 05:42 PM
This is a big black hole..

It would be nice to test equality of for example MuleEvent between different mule instances (e.g. serialization) but in order to do that practically everything in Mule needs to implement equals()/hashCode(). I started down this road thinking it would be good to have them anyway, but then realized just how much there would be to do and that the only reason for doing it was to this specific unit test and decided to back out.

We should probably only implement equals()/hashCode() on an as needed basis for implementation and not implement them just for unit testing.

Leaving open for thoughts/comments..


Daniel Feist added a comment - 30/Nov/08 07:00 PM
This isn't required and even if you try to implement these it become a never ending tree of types that need equals implementing.