Its not intended for storing in lists/queues etc. Its just for serializing / deserializing an exchange for transfer over the wire. Also each holder ought to be unique as you shouldn't really create multiple holders of the same exchange. And each exchange in Camel is unique.
On Tue, Apr 29, 2014 at 10:54 AM, Gerda Ilger <gerda.il...@ecosio.com> wrote: > Hi all, > > We're using hazelcast:seda with the option "transferExchange=true", which > works great for moving our data over the wire. > > I'm currently working on plain java code for moving exchanges between > hazelcast queues, and I ran into the following problem: > Some operations on the hazelcast queue, like 'remove(obj)' and > 'contains(obj)', don't work because DefaultExchangeHolder does not have an > implementation of 'equals'. > > Is there a reason why DefaultExchangeHolder does not implement 'equals'? > > We're on Camel 2.13. > > Thanks, > Gerda -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
