camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: Failed to build body from content. Serializable class not available to broker
Date Fri, 08 Jul 2011 07:00:20 GMT
On Thu, Jul 7, 2011 at 11:44 AM, Andrè <morpheusandre@web.de> wrote:
> yes, i do or shouldnt i do that ??
>
> (context:i´m trying to use the topic as a many/many thing..., where
> producers send and one consumer responds and a other just listens, which
> should as close as possible to JMS (thats why i dont use a wiretap))
>

You can disable camel-jms to map the received message.

You can add this option to the uri in broker A
mapJmsMessage=false

You can read about this option at
http://camel.apache.org/jms

But you will still have the problem that broker B send back a reply as
a Java Object, and that Java Object class is not on the classpath on
broker A. So you would need to copy the JAR  that has those classes to
broker A as well.


> --
> View this message in context: http://camel.465427.n5.nabble.com/Failed-to-build-body-from-content-Serializable-class-not-available-to-broker-tp4556486p4560507.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>



-- 
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/

Mime
View raw message