Hi 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): http://docs.oracle.com/javase/6/docs/api/java/lang/Object.html#equals(java.lang.Object) http://docs.oracle.com/javase/6/docs/api/java/lang/Object.html#hashCode() Babak -- View this message in context: http://camel.465427.n5.nabble.com/MockEndpoint-assertIsSatisfied-Object-Object-tp5716388p5716398.html Sent from the Camel Development mailing list archive at Nabble.com.
