Hi Yeah sounds like we can just be Object, Object.
Fell free to log a JIRA and submit a patch. http://camel.apache.org/contributing.html On Fri, Sep 13, 2013 at 11:01 PM, HrvojeM <[email protected]> wrote: > Hi, > > the class org.apache.camel.component.hazelcast.listener.CamelEntryListener > within the module camel-hazelcast directly implements > com.hazelcast.core.EntryListener<String,Object> instead of keeping the > key/value types generic. Registering this listener to a Hazelcast maps with > other key types than String rises a ClassCastException. > So using camel-hazelcast limits the allowed types of keys for Hazelcast maps > to Strings. IMO this is a bug - is anybody aware of this? I didn't find an > issue for that. > > Best regards, > > > > > ----- > -- > HrvojeM > -- > View this message in context: > http://camel.465427.n5.nabble.com/camel-hazelcast-CamelEntryListener-limits-usage-of-Hazelcast-maps-tp5739340.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: [email protected] Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
