Hey guys,
I am new to Camel. Currently, I want to use PropertyPlaceholderConfigurer to
specify the autoStartup option in Camel route. Here is the
PropertyPlaceholderConfigurer bean:
Use the concurrentConsumers option in the JMS consumer to start multiple
receiving threads.
Make sure to use the transacted mode to leverage broker-side redeliveries.
Like Claus said above, use JMS Message Groups to serialize the processing
of messages that share a key. If your producer cannot pl
I assume the idea is that you configure an existing
com.hazelcast.core.HazelcastInstance on the HazelcastComponent which
is then used.
And the com.hazelcast.core.HazelcastInstance can refer to an external HC server.
Though would be nice with some docs how to do that.
On Sat, Jul 13, 2013 at 12:1
Hi
Yeah we love contributions. See here
http://camel.apache.org/contributing.html
On Fri, Jul 12, 2013 at 10:58 AM, per.ce...@gmail.com
wrote:
> Hi again,
>
> Is this problem existing, due to camels own XsltUriResolver?
> It seems that camels XsltUriResolver only is capable to handle files
> eit
It appears that it creates a local HC server on-the-fly, but I'd like to have
it use my remote HC server. Is that possible?
--
View this message in context:
http://camel.465427.n5.nabble.com/does-hazelcast-component-support-stand-alone-HC-server-tp5735586.html
Sent from the Camel - Users maili