It looks like you may also need to add the apache commons-csv jar to your
class path. This is one of the dependencies of the camel-csv jar:
org.apache.servicemix.bundles/org.apache.servicemix.bundles.commons-csv
Jared
--
View this message in context:
http://camel.465427.n5.nabble.com/Using-ca
Actually that also does not work for object messages. Camel will still try
to deserialize the object in the body.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-route-only-dealing-with-headers-tp5736452p5736502.html
Sent from the Camel - Users mailing list archive at
I know object messages are not the best, but there are some places in our app
that we do still use them. I'm building a simple utility that should be
able to take any message, do some header manipulation, and then pass on the
message to another consumer. I got my tests to pass by using
from("acti
I have a route that listens on an ActiveMQ endpoint and only manipulates
exchange headers. I don't care about the body of the exchange at all.
Consequently, I don't want to have to
marshal/unmarshal/serialize/deserialize the body at all, but just send it
along to anything downstream. Particularl
