You are fundamentally misunderstanding the way that Camel works. Camel is
built around the concept of an Exchange which is what is passed from one
processor to another. Each link in the chain of a route implements the
Processor interface where it receives an Exchange and modifies it or
possibly pro
I have to take in two files as input because the 3rd party custom mapping
route is expecting two arguments ( both as byte[] )
So the example would be
--
View this message in context:
http://camel.465
You could put the logic to handle the 2 files in an AggregationStrategy
implementation and then depending on which makes more sense use it in an
Aggregator (in the case where you really have 2 routes) or in a content
enricher (where there is a main flow and you are just loading the second
file for
Why do you need a Camel route for that?
On Fri, Aug 23, 2013 at 5:05 PM, nanotech wrote:
> Hi,
>
> I have an requirement where I need to send two files as input to a third
> party mapping jar. These files are the two arguments that the underlying
> mapping jar is expecting.
>
>
> Can someone sug
