Provides Apache Camel integration with the WildFly Application Server.
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.
If you like to contribute to the docs, please file a pull request against the next version branch.
Minimum of Java 1.7, to run WildFly and Maven.
Minimum of Maven 3.2.3.
The default build is straight forward
$ mvn clean install
The extended build includes the set of JavaEE integration examples
$ mvn clean install -Dts.all
If you like to contribute to the project, please file a pull request.
Simply apply the wildfly-camel-patch to a compatible wildfly version.
If you use the wildflyext/wildfly-camel docker distribution this step does not need to be performed.
In your WildFly home directory run ...
$ bin/standalone.sh -c standalone-camel.xml
or simply run the docker image like this ...
$ docker run --rm -ti -p 9990:9990 -p 8080:8080 -e WILDFLY_MANAGEMENT_USER=admin -e WILDFLY_MANAGEMENT_PASSWORD=admin wildflyext/wildfly-camel
Access WildFly Management Console at http://192.168.59.103:9990 and the Hawtio console at http://192.168.59.103:8080/hawtio
Docker images and related testsuites are included if you have DOCKER_IP and DOCKER_HOST environment variables.
On a Mac you would automatically have those when you run the build in a boot2docker shell.
DOCKER_CERT_PATH=~/.boot2docker/certs/boot2docker-vm
DOCKER_HOST=tcp://192.168.59.103:2376
DOCKER_IP=192.168.59.103
DOCKER_TLS_VERIFY=1
On Linux you may have to set these environment variables yourself
DOCKER_HOST=tcp://127.0.0.1:2375
DOCKER_IP=[host ip]
Make sure the docker deamon binds to a socket for a client to connect to
$ docker -d -H tcp://127.0.0.1:2375