JBoss development,
A new message was posted in the thread "Camel integration input requested":
http://community.jboss.org/message/529672#529672
Author : Edgar Silva
Email : edgarsilva(a)gmail.com
Profile :
http://community.jboss.org/people/edgar.silva
Message:
--------------------------------------------------------------
Hi David,
This is very interesting, and I also vote for this idea. I've been doing some initial
working on this at
http://code.google.com/p/breakingwoods. What we have done for awhile is
basically to listen some routes (URIs) from Apache Camel. I believe some components can be
just "Event Producers", but several others can be even the final destinations,
for instance, I am figuring out an way to create a kind of "CamelNotifier", that
can use the ready Camel infrastructure.
Looking from a developer perspective, downloading or building the actual Apache Camel
Suppor for JBoss ESB 4.7 hosted at breakingwoods, anybody can just add the "Apache
Camel Gateway/Listener" according the following XML config in jboss-esb.xml service
section:
{code:xml}
<listener name="ApacheCamel" busidref="ApacheCamel"
is-gateway="true">
<property name="gatewayClass"
value="org.jboss.soa.esb.listeners.gateway.camel.ApacheCamelListener" />
<property name="protocol-uri"
value="irc:mailto:breakingwoods@irc.freenode.net/#esbtest" />
<property name="destination-category"
value="sample-apachecamelESBService" />
<property name="destination-name"
value="sample-apachecamelESBServiceListener" />
</listener>
{code}
The class
http://code.google.com/p/breakingwoods/source/browse/trunk/jbossesb-apach...
, is the listener based on +AbstractThreadedManagedLifecycle+, which is responsible to
interact with Camel, the other properties are useful for the following purposes:
* protocol-uri - This is the Apache Camel URI that will receive the Events and the message
itself, this message will be forwarded to JBoss ESB Services pipelines. +
+
* destination-category - Service Category that will receive the message arrived from Camel
layer
* destination-service - The Service that will handle the message arrived from Camel, this
service for instance can be a simple Smooks CBR, or anyother able to marshal or unmarshal
the message.
As David said, Camel is not an ESB, but I consider it a valuable piece for any solution
that aims to promote integration in any kind of architecture.
Cheers
Edgar
--------------------------------------------------------------
To reply to this message visit the message page:
http://community.jboss.org/message/529672#529672