On Sat, Dec 5, 2009 at 10:31 AM, Hendy Irawan <[email protected]> wrote:
>
> Hi,
>
> I was trying to make a publish-subscribe mechanism by using (only)
> @EndpointInject and @Consume, so that I can have somewhat POJO style routing
> with minimal XML configuration.
>
> It turned out that this didn't work because multiple consumers don't work
> with this setup.
>
> After reading http://camel.apache.org/publish-subscribe-channel.html it
> seems that there are only three ways Camel supports Publish Subscribe:
> 1. JMS Topic
> 2. XMPP Room
> 3. Explicit routes via multicast
>
> Option 1 and 2 is overkill because it requires external server.
>

Maybe spring event can be used also?
http://camel.apache.org/event.html


> So the functionality is basically there in Camel (option 3), however, I
> cannot do it dynamically because it involves explicitly setting up the
> routes, instead of doing it dynamically via @Consume.
>

You can create you own component that offers topic like functionally.
You could extend the seda or direct component and implement the logic
missing.


> Spring Integration seem to support this by allowing to create a
> PublishSubscribeChannel explicitly.
>
> Is it planned to support easy "dynamic" Publish Subscribe Channel via
> annotations (i.e. without explicit configuration)? Thank you.

I would assume adding @Consume to any POJO does not require any routes
to pre existing and cannot see why its not dynamic.


Why dont you create a small sample what you want as its easier to
discuss based on that.

And we love contributions
http://camel.apache.org/contributing.html

Just see Camel 2.1 which have 5 or so new components all contributed by others.


> --
> View this message in context: 
> http://old.nabble.com/Implementing-Publish-Subscribe-Channel-tp26654086p26654086.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>



-- 
Claus Ibsen
Apache Camel Committer

Author of Camel in Action: http://www.manning.com/ibsen/
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus

Reply via email to