You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Maurice <ma...@betzel.net> on 2013/08/16 10:35:43 UTC
Externalizable and the activemq classpath
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.
Re: Externalizable and the activemq classpath
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
There is a ActiveMQ mailing lists where this question is better posted.
On Fri, Aug 16, 2013 at 10:35 AM, Maurice <ma...@betzel.net> wrote:
> 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.
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen