camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: Setting HMS property
Date Tue, 12 Jan 2010 17:11:36 GMT
On Tue, Jan 12, 2010 at 4:34 PM, Drone42 <> wrote:
> I want to publish messages on a set of JMS queries, using the
> publish-subscribe pattern to route messages to interested consumers. My
> messages are simple POJOs (basically parameters), subtyped based on an ID. I
> have thousands of subtypes. Each consumer will typically be interested in
> maybe 100 of these.
> Question 1; What is most performant
> 1. Having a topic per subtype and the consumers listening to a subset. I
> will in this case have thousands of topics.
> 2. Having one topic into which all messages go and use a JMS message
> property and a selector per consumer?
> Looking at the net for performance evaluations it seems a general problem
> for JMS implemenations to handle many topics.
> Assuming that answer 2 is the way to go...
> Question 2: Can I automatically set the ID as a property in the JMS message
> as part of the Camel route? The ID is available as an attribute with
> getters/setters in my POJO. Is there a component that already does this, or
> will I have to create my own messageConverter?

You can use the setHeader DSL to set an header.

To get the data from your pojo you can invoke a bean which returns it,
or use scripting language.

I do want in the future to improve simple language in Camel to have a
light weight getter support for POJOs. It does not support that

> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

Claus Ibsen
Apache Camel Committer

Author of Camel in Action:
Open Source Integration:

View raw message