camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: SEDA vs JMS/ActiveMQ
Date Thu, 30 May 2013 05:43:40 GMT
For you JAXB classes you can use javax.jmx.TextMessage as the type.
Then the data is a String in XML format.
If you have camel-jaxb on the classpath then Camel can automatic
marshal from POJO via JAXB to XML as a String.

To force use TextMessage you can configure the JMX endpoint with

But still when you use JMS then the JMS spec has limitations of what
type can be used. See the details on the Camel JMS page.

On Wed, May 29, 2013 at 3:38 PM, Cristiano Costantini
<> wrote:
> Hello,
> I've been prototyping my application using SEDA and I wrote routes with
> endpoints using this component.
> Now I've started to make some tests using an embedded ActiveMQ and
> substituting the seda: endpoints with jms: or activemq:
> Of course! I've started getting many errors as I was using custom classes
> both as body and headers in camel Exchanges.
> I'm not an expert at all of JMS or ActiveMQ, but I need it to
> implement Guaranteed Delivery and Durable Subscriber patterns.
> How should I deal with serialization of classes in body and headers when
> using ActiveMQ? (my classes don't implement Serializable but are annotated
> with JaxB and can be marshalled/unmarshalled)
> Do you know any web resource which I can study to learn using ActiveMQ for
> my needs?
> Thank you again,
> Cristiano

Claus Ibsen
----------------- The open source integration conference.

Red Hat, Inc.
FuseSource is now part of Red Hat
Twitter: davsclaus
Author of Camel in Action:

View raw message