camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Babak Vahdat <>
Subject Re: MockEndpoint.assertIsSatisfied(Object, Object)
Date Tue, 24 Jul 2012 13:21:19 GMT

No! Don't let it baffle you. The usage of the "==" operator as the first
step is just because of the optimization & performance. A proper usage of
the equals() method is at the bottom of the method you mentioned.

So just override the equals() & hasCode() methods properly and then you're
on the right track. And also make sure you don't break the expected contract
below (see javadoc):


View this message in context:
Sent from the Camel Development mailing list archive at

View raw message