This behavior hasn't changed between 2.4 and 2.5. The behavior that you're
experiencing with 2.5 should also occur when using 2.4. What you have is a
pipeline while you should be using a multicast. The following code behaves
like you expect as described under 2.4:
from("{{export.queue}}")
.transacted()
.setHeader(MessageStatusConverter.STATUS,
constant(MessageStatuses.PROCESSING))
.multicast()
.to("jpa:au.com.zurich.phoenix.gateway.domain.MessageStatus")
.to("xslt:stylesheets/Main.xsl")
Take a look at the EIP patterns (pipes and filters, multicast, etc) as Claus
suggested. More details about EIP can be found in the Camel in Action book.
-----
Richard Kettelerij,
http://github.com/rkettelerij
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-2-5-JPA-Difference-From-2-4-tp3249404p3250919.html
Sent from the Camel - Users mailing list archive at Nabble.com.
