Description of problem:
Camel has examples that seem not to work with EAP, even when deployed as a fully-encapsulated .war.
Example: Using JBDS, start a new Fuse project and choose the Camel-webconsole archetype. Deploy the result to Jetty (which should work), then EAP (which should fail).
Please fix these and ensure they run against the version of EAP packaged with FSW. Examples of this type will be of high value, as there is little documentation about running Camel-on-EAP compared to the wide functionality it offers.
See the related Fuse Issue Tracker at .
Andrea Cosentino <firstname.lastname@example.org> updated the status of jira ENTESB-1744 to Resolved