The Camel routes used in this example are explained by the following diagram:
- Install JBoss Developer Studio 8.1.0 [https://www.jboss.org/products/devstudio.html]
- Install Apache Maven 3.2.x [http://maven.apache.org]
- Install JBoss Fuse 6.3.0 [https://www.jboss.org/products/fuse.html]
- Build this project so bundles are deployed into your local maven repo
$ mvn clean install
- Start JBoss Fuse
$ bin/fuse
- Add this projects features.xml config to Fuse from the Console (makes it easier to install bundles with all required dependencies)
JBossFuse:karaf@root> features:addUrl mvn:org.fusesource.examples/rider-auto-common/5.0-SNAPSHOT/xml/features
- Install the project.
JBossFuse:karaf@root> features:install rider-auto-osgi
- To test the file processing, there are existing files in the rider-auto-common module.
$ cp rider-auto-common/src/data/message1.xml /target/placeorder
To see what happened look at the log file, either from the console
JBossFuse:karaf@root> log:display
or from the command line
$ tail -f data/log/fuse.log
- To test the WS, use your favorite WS tool (e.g. SoapUI) against the following WSDL hosted by the rider-auto-ws bundle.
If you hit any problems please let the Fuse team know on the forums [https://community.jboss.org/en/jbossfuse]