Camel subsystem on WildFly

[thomas.diesler]

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 to the subsystem and added support for the WildFly domain mode.

A new set of standalone examples shows how to use Camel in the context of JavaEE applications.

Ready available docker images are published as wildflyext/wildfly-camel.

For details, please have a look at the release notes.

cheers

—thomas

[ctomc]

hey,

any reason why not use wildfly-extras org group on github that is mean for all wildfly extensions / extras that are not part of main repo and are maintained by community? if you are interested, let me know. wildfly-extras · GitHub

[thomas.diesler]

Yes, we can move. wildflyext has funnily enough the same connotation ;-)

James Netherton and I need to be in a team that have write access

[ctomc]

done, repo: https://github.com/wildfly-extras/wildfly-camel

and you and James are members of the team that has all the permissions in this repo