Hi Robin,
You should be in good shape with clustered quartz scheduling and the
servlet endpoints fronted by a load balancer. Could you provide some
more information about the "route manipulation through user
interaction"? Describing this requirement more fully may lead to more
and better respons
Hi Matthieu,
A new broker is being created because you have an defined
in your blueprint context.
You should remove this element if you do not want a new broker to be
created by the blueprint container.
Next, you will ned to include a jmsConnectionFactory in the activemq bean,
which indicates t
it a try and provide comments as useful.
Thanks,
Rich
On Tue, Aug 28, 2012 at 10:49 PM, Rich Newcomb wrote:
> Hi Dominik,
>
> The example you provided is a little bit confusing. The PUBLIC key of the
> recipient is applied for asymmetric encryption. So, there no need to
> acce
Hi Dominik,
The example you provided is a little bit confusing. The PUBLIC key of the
recipient is applied for asymmetric encryption. So, there no need to
access a password-protected key when the data is being marshalled.
However, the recipient will use a PRIVATE key from a key store to decrypt
You can use the .log in your routes, via the log EIP (
http://camel.apache.org/logeip.html).
I tested the route segment supplied in the original message (via
Camel 2.6.0-fuse-01-09) ::
.setBody().simple("Say Hello")
.log(LoggingLevel.DEBUG, "Message body: ${body}")
.. and it works as expe
Check out the camel bean binding docs [1].
With the Simple language you can do something like this:
from("mms:topic:edaXmlTopic").bean(EventStoreService.class,
"storeEventXmlToTCCache(${body}, ${header.someHeader})")
1. http://camel.apache.org/bean-binding.html
On Tue, Jan 24, 2012 at 11
Have a look at the camel aggregator EIP [1]. You can receive messages from
your JMS response queue and then use the JMSCorrelationID header value in
your aggregation expression. Note that you will need to select and
configure an aggregation strategy. For example, if you want to use a 5
second ti
The ftp consumer produces a WARN message by default when the connection
fails - instead of throwing an exception.
You can use the throwExceptionOnConnectionFailed property to change this
behavior, and then handle the thrown exception from the
PollingConsumerPollStrategy[1] rollback() method.
Note
If you like the JMS delivery model and you are using ActiveMQ as your
message broker, you could subscribe to the topic as a retroactive consumer
[1] and apply a "Last Image Subscription Policy" [2] on the broker to ensure
that your subscribers receive the most recent message that was sent on the
to
