Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1297858

Summary: Camel Work Item Handler Documentation is Wrong and Inadequate
Product: [Retired] JBoss BPMS Platform 6 Reporter: Justin Holmes <jholmes>
Component: DocumentationAssignee: Dawn Eisner <deisner>
Status: CLOSED EOL QA Contact: Lukáš Petrovický <lpetrovi>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: brms-docs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 19:33:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Justin Holmes 2016-01-12 16:19:23 UTC 
Document URL: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse/6.2.1/html/Integration_Guide/install_kie_camel_pack.html

Section Number and Name: JBOSS BPM CAN INVOKE CAMEL

Describe the issue: To describe the usage of the camel work item handler, the documentation points to the JMS section of the development guide (https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_BPM_Suite/6.2/html-single/Development_Guide/index.html#sect-JMS). This doesn't make any sense, as these camel work item handler and the JMS service endpoints are completely unrelated.

Suggestions for improvement: Provide a working example of how to use the Camel Work Item handler to do basic integration tasks. This should not require installation of the integration pack, but rather a simple KJar dependency.

https://github.com/jboss-integration/fuse-bxms-integ/blob/master/camel/jbpm-workitems-camel/src/main/java/org/jbpm/process/workitem/camel/CamelHandlerFactory.java

Additional information: Don't both fixing the existing docs. Please get a submission into the community upstream which in future versions will provide the source for the product docs. I am happy to collaborate if there are concerns.