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

Bug 1151096

Summary: Camel service task fails on bpmn process created by jBPM Designer
Product: [Retired] JBoss BPMS Platform 6 Reporter: Radovan Synek <rsynek>
Component: jBPM CoreAssignee: Kris Verlaenen <kverlaen>
Status: CLOSED EOL QA Contact: Radovan Synek <rsynek>
Severity: high Docs Contact:
Priority: high    
Version: 6.1.0CC: kverlaen
Target Milestone: ER2   
Target Release: 6.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 18:39:35 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:
Attachments:
Description Flags
error stacktrace none

Description Radovan Synek 2014-10-09 15:06:42 UTC 
Created attachment 945350 [details]
error stacktrace

Description of problem:
Designer puts TaskName as another parameter of any task (including Camel service task), however this parameter is passed to Camel via URI by CamelHandler. Camel throws an org.apache.camel.ResolveEndpointFailedException as a result. Full stacktrace is in the attachment.

How reproducible:
reproducer is a part of PR https://github.com/droolsjbpm/jbpm/pull/212
take a look at e.g. CamelFileTest

Additional information:
Is TaskName a mandatory parameter for jBPM engine? Removing corresponding data input association fixed the problem. If it is indeed mandatory, it need to be removed by CamelHandler before sending to Camel.
Comment 1 Kris Verlaenen 2014-10-31 02:29:47 UTC 
master: https://github.com/droolsjbpm/jbpm/commit/089fbf76a2bd6822f1f7af673a187b7b455b3362
6.2.x: https://github.com/droolsjbpm/jbpm/commit/425021e708961deef44e38b366a3e5ea361ca2a9
Comment 2 Radovan Synek 2015-01-05 08:19:55 UTC 
Verified with BPMS-6.1.0.ER3