Hi David,

This is very interesting, and I also vote for this idea. I've been doing some initial working on this at breakingwoods project. 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:breakingwoods@irc.freenode.net/#esbtest" />
 <property name="destination-category" value="sample-apachecamelESBService" />
 <property name="destination-name" value="sample-apachecamelESBServiceListener" />
</listener>
{code} 

The class org.jboss.soa.esb.listeners.gateway.camel.ApacheCamelListener , 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

Hi Edgar,

The gateway/listener is placed inside a service right? Why not use the internal parameters for the destination instead of configured parameters?

so instead of:

<listener name="ApacheCamel" busidref="ApacheCamel" is-gateway="true">
 <property name="gatewayClass" value="org.jboss.soa.esb.listeners.gateway.camel.ApacheCamelListener"></property>
 <property name="protocol-uri" value="irc:breakingwoods@irc.freenode.net/#esbtest"></property>
 <property name="destination-category" value="sample-apachecamelESBService"></property>
 <property name="destination-name" value="sample-apachecamelESBServiceListener"></property>
</listener>

this would be:

<listener name="ApacheCamel" busidref="ApacheCamel" is-gateway="true">
 <property name="gatewayClass" value="org.jboss.soa.esb.listeners.gateway.camel.ApacheCamelListener"></property>
 <property name="protocol-uri" value="irc:breakingwoods@irc.freenode.net/#esbtest"></property>
</listener>

where as the retrieval of the parameters would be changed from:

{code}
String serviceCategory = listenerConfig.getRequiredAttribute(DESTINATION_CATEGORYNAME_TAG);
String serviceName = listenerConfig.getRequiredAttribute(DESTINATION_SERVICENAME_TAG);
{code}

to:

{code}
String serviceCategory = ListenerUtil.getValue(config, ListenerTagNames.SERVICE_CATEGORY_NAME_TAG);
if (Util.isNullString(serviceCategory))
{
 throw new ConfigurationException("No service category defined!") ;
}
 
String serviceName = ListenerUtil.getValue(config, ListenerTagNames.SERVICE_NAME_TAG) ;
 
if (Util.isNullString(serviceName))
{
  throw new ConfigurationException("No service name defined!") ;
}
 
{code}

Or am I missing something here?

Regards,

Hans

{code:xml}
<service category="Custom" name="Listener" description="" invmScope="GLOBAL">
 
<listeners>
 
<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:breakingwoods@irc.freenode.net/#esbtest" />
  <!--  property name="protocol-uri" value="file:///home/esilva/esb/camel/inbox?noop=true" /> -->
  <property name="destination-category" value="sample-apachecamelESBService" />
  <property name="destination-name" value="sample-apachecamelESBServiceListener" />
 
  </listener>
</listeners>
 
<actions mep="OneWay">
 
<action name="dump"
class="org.jboss.soa.esb.actions.SystemPrintln">
  <property name="printfull" value="false" />
</action>
</actions>
 
</service>
{code}

Based on your tips, I will improve this gateway source at breakingwoods SVN  now

Thanks

Hi Edgar,

Can I join the  breakingwoods club, and if so, how?

Regards,

Hans

Easy, just send me your gmail account and we will add you there!

We would love have your help there!

Edgar

David and friends,

Seems that this discussion will go far away

http://jazoon.com/Conference/Wednesday/Silva

I was approved to be speaking at Jazoon, thanks Tom Fenelly for reviewing my paper

And please, If you also wanna see some like that in US, please vote for my session during JUDConf here:

https://community.jboss.org/poll.jspa?poll=1042

This session is pretty close what I will gonna show at Jazoon in Zurich.

Thank you

Edgar

Well done Ed.... and vote cast

Hi Edgar,

I have made the changes locally (as earlier explaned) to the camel listener but haven't had the time to check if it works ok. As soon as I can find the time I will test the code and after a succesfull test I will check it in, and you can see if you like it.

Regards,

Hans

Just had a quick look at it and my only comment at the moment is that we would be unlikely to add that to 4.x as it stands, certainly not with the camel/camel-context part of the schema.  It would appear that area is really a camel configuration in another guise and this would be better handled (in 4.x) through the normal camel mechanisms.

This does look promising for 5.x though.

Kev

David,

Awesome job man! Congratulations, I am really happy with this kind of directions that ESB is taking!

If we get Camel, add some annotation stuff, an effective monitoring stuff out of the box (JOPR/JON) on JBoss App Server 6.0, our ESB will be a really cool solution for integrating scenarios (SOA).

Keep going !

Cheers

Edgar

Dave, another twist on this could be a new <camel-listener> in the ESB, which lists a series of "from" addresses:

<listeners>
    <jms-listener ....>

    <camel-listener from="file://xxx" />
    <camel-listener from="ftp://aaaaa" />
</listeners>

And then in the listener intialization, you programatically create the camel context and routebuilder, routing from the specified from endpoint, to the service in question....

from(configuredFromEndpoint)
    .to("jbossesb://service?category=<theservicecat>&name=<theservice>");

And then maybe a CamelRouter action for routing to Camel endpoints.

Just a thought.