Does activeMQ need our self created classes on its classpath if i externalize these objects into java primitive types? My research sofar indicates that a jms message type of bytestream with externalize should do the trick to avoid the classpath issue.
-- View this message in context: http://camel.465427.n5.nabble.com/Externalizable-and-the-activemq-classpath-tp5737384.html Sent from the Camel - Users mailing list archive at Nabble.com.
