You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@camel.apache.org by Thomas Diesler <td...@redhat.com> on 2014/12/01 11:45:36 UTC

Camel subsystem on WildFly

Folks, 

I’m happy to announce the availability of the Camel subsystem for WildFly. 

The WildFly-Camel Subsystem allows you to add Camel Routes as part of the WildFly configuration. 
Routes can be deployed as part of JavaEE applications. JavaEE components can access the Camel Core API and various Camel Component APIs.
Your Enterprise Integration Solution can be architected as a combination of JavaEE and Camel functionality.

We added a number of new camel components <http://wildflyext.gitbooks.io/wildfly-camel/content/components/README.html> to the subsystem and added support for the WildFly domain mode. 
A new set of standalone examples <https://github.com/wildflyext/wildfly-camel/tree/2.0.0.CR1/examples> shows how to use Camel in the context of JavaEE applications. 
Ready available docker images are published as wildflyext/wildfly-camel <https://registry.hub.docker.com/u/wildflyext/wildfly-camel/>.

For details, please have a look at the release notes <https://github.com/wildflyext/wildfly-camel/releases/tag/2.0.0.CR1>.

cheers
—thomas

Re: Camel subsystem on WildFly

Posted by Daniel Pocock <da...@pocock.pro>.

On 01/12/14 11:45, Thomas Diesler wrote:
> Folks, 
>
> I’m happy to announce the availability of the Camel subsystem for WildFly. 
>
> The WildFly-Camel Subsystem allows you to add Camel Routes as part of the WildFly configuration. 
> Routes can be deployed as part of JavaEE applications. JavaEE components can access the Camel Core API and various Camel Component APIs.
> Your Enterprise Integration Solution can be architected as a combination of JavaEE and Camel functionality.
>
> We added a number of new camel components <http://wildflyext.gitbooks.io/wildfly-camel/content/components/README.html> to the subsystem and added support for the WildFly domain mode. 
> A new set of standalone examples <https://github.com/wildflyext/wildfly-camel/tree/2.0.0.CR1/examples> shows how to use Camel in the context of JavaEE applications. 


I had a quick look over these, I notice they all build WAR files

Is that the only packaging that is tested/supported?

For a project that has no web interface (e.g. just consuming from JMS
queues) can this be deployed like a regular EJB3 JAR inside an EAR
file?  Or even a standard JAR inside an EAR file?