Right now, we are accepting any suggestion, contribution, testing, complains... money etc, anything you judge valuable for make this component a really useful new JBoss ESB 4.7 Component.
Basically what was done is just a new Gateway that is able to listen the Apache Camel Components, for awhile we just tested two of those: File and IRC.
IRC can be a good way to receive events or messages that can be delivered to an existing JBoss ESB Service, in other words, this is the finnest integration between these two opensource projects: JBoss ESB and Apache Camel, and the community behind breakingwoods is happy to deliver this new component.
How it Works
First of all, we need just to declare a new Service, that will be listener for Apache Camel.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<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> |
The properties for this components are the following:
- protocol-uri : Apache Camel Endpoint URI
- destination-category : Service Category that will receive the events from the Camel Layer
- destination-name: Service that will process the event that happened on Camel Layer
We hope that the community enjoy this!
Check it out in http://code.google.com/p/breakingwoods