Re: Hazelcast Component persistence

2011-10-21 Thread Ioannis Canellos
Yes, this would be enough. Please note, that you will still need to configure the instance that you pass to the component. -- *Ioannis Canellos* * FuseSource http://fusesource.com ** Blog: http://iocanel.blogspot.com ** Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix

Re: Hazelcast Component persistence

2011-10-20 Thread bvysocky
? bean id=hazelcast class=org.apache.camel.component.hazelcast.HazelcastComponent property name=hazelcastInstance ref=hazelcastInstance/ /bean Thanks, Brian Vysocky -- View this message in context: http://camel.465427.n5.nabble.com/Hazelcast-Component-persistence-tp4911607p4923120

Re: Hazelcast Component persistence

2011-10-18 Thread Ioannis Canellos
There is a pending patch for commit, which would allow the hazelcast component to be passed an existing Hazelcast instance. Once this is committed you will be able to configure Hazelcast with any way you want and just pass it to the component. -- *Ioannis Canellos* * FuseSource

Hazelcast Component persistence

2011-10-17 Thread bvysocky
daos for the queue persistence. Is it possible to configure the hazelcast cluster in spring when using this component? Camel Version 2.8.0 Java Version 1.6 Thanks, bvysocky -- View this message in context: http://camel.465427.n5.nabble.com/Hazelcast-Component-persistence-tp4911607p4911607.html

Re: Hazelcast Component persistence

2011-10-17 Thread Claus Straube
, bvysocky -- View this message in context: http://camel.465427.n5.nabble.com/Hazelcast-Component-persistence-tp4911607p4911607.html Sent from the Camel - Users mailing list archive at Nabble.com.