ActiveMQObjectMessage.getObject(ActiveMQObjectMessage.java:184)
> ... 21 more
>
>
> Copying the library containing the type into the library path of activemq
> solves the problem, but I wonder why the routing depends on knowledge of the
> class? Why cant I route any message
generic manner? Why does the 'middleware' activemq have to
know about the types I route in my business tier?
--
View this message in context:
http://camel.465427.n5.nabble.com/Class-not-found-when-Creating-Camel-route-through-Activemq-console-tp4289185p4289185.html
Sent from the Camel - Users mailing list archive at Nabble.com.
