camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mfrenzel <mirco.fren...@gmx.de>
Subject Splitter EIP Best Practice
Date Thu, 19 May 2016 12:59:33 GMT
Hello everyone, this is my first post and I am seeking the opinion of more
experienced camel users.
In my route, I split up the content of a zip file and determine the
completeness of it`s content by using the aggregator EIP, which applies
certain business rules in it`s completion predicate. 
So far so good I think. After that I have to send individual REST calls for
each file contained in the original zip, so I split up again what has been
aggregated and set 
necessary http headers inside the splitters split method.

Here are my questions to you: 
first: when you need to determine (business rule) completeness of some data
items, but need those items as individual messages afterwards...is
aggregating to determine completeness 
and splitting up afterwards the way to go?
second: when splitting up merged data of some kind, is it bad practice to do
something else on the split up messages (i.e. setting http headers) while
you`re at it in the split method? 
I considered adding another bean/processor after the splitter to produce
mainly redundant code, that`s why I did it in the splitter.

thx for your time



--
View this message in context: http://camel.465427.n5.nabble.com/Splitter-EIP-Best-Practice-tp5782787.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Mime
View raw message