Time is the best teacher. :)
I've found a way to do a processing message after activity receives it - with
interceptors. There some exceptions, but both persistence and processing works.
Solutions looks next:
interceptFrom("activemq:incoming")
.split(body())
.multicast()
Hey Hadrian,
I started investigating the camel-bam code and one from statements I wrote is
not true. The Process name can be set by calling the ProcessBuilder
constructor. The Process-N name is a default behaviour.
Also, if it makes a sense to support delaying the activity? Eg making an
activit
Lukasz, do you mind opening a jira with your findings?
Thanks, Hadrian
On 01/10/2012 06:36 PM, Łukasz Dywicki wrote:
Hey everyone,
I tried yo use camel-bam and it works for very basic example shown in
documentation. It works well for correlating the files without any middle
processing steps.
