Willem - thanks for the reply, Currently we are using the camel 2.0.0 libraries that came bundled with ActiveMQ 5.3 bundle. I have put my message classes in the classpath of ActiveMQ and my routes now work - but I am hoping not to be bound by this dependency.
Previously using ActiveMQ 5.2 bundled with camel 1.5 libraries we were able to send any object to a queue and route via camel without that class being on the classpath. I was hoping that there may be an argument/configuration that would avoid de-serializing the message in camel. -- View this message in context: http://old.nabble.com/Camel-Route-causes-Serializable-class-not-available-to-broker-tp27358773p27373089.html Sent from the Camel - Users mailing list archive at Nabble.com.
