Bug 1124028 - Please ensure Camel works with provided examples
Summary: Please ensure Camel works with provided examples
Keywords:
Status: NEW
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: Camel
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact: Matej Melko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-28 20:47 UTC by Rick Wagner
Modified: 2021-10-15 11:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ENTESB-1744 0 Major Resolved Please change Camel archetypes so they run on EAP (especially as used by FSW) 2016-10-11 08:21:45 UTC

Description Rick Wagner 2014-07-28 20:47:08 UTC 
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 [1].


[1] https://issues.jboss.org/browse/ENTESB-1744
Comment 3 JBoss JIRA Server 2016-10-11 08:21:45 UTC 
Andrea Cosentino <ancosen1985> updated the status of jira ENTESB-1744 to Resolved
Note You need to log in before you can comment on or make changes to this bug.