Bug 1328687

Summary:	[RFE] business rule task supports boundary error event
Product:	[Retired] JBoss BPMS Platform 6	Reporter:	Gary Hu <ghu>
Component:	jBPM Core	Assignee:	Alessandro Lazarotti <alazarot>
Status:	CLOSED EOL	QA Contact:	Radovan Synek <rsynek>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	unspecified
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 20:13:20 UTC	Type:	Feature Request
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Gary Hu 2016-04-20 04:13:15 UTC

Our documentation suggests to use the boundary error event for handling the exception occurred in a workflow process.  
If a boundary error event is used for a business rule task the following exception is thrown:
  java.lang.ClassCastException: org.jbpm.workflow.core.node.RuleSetNode cannot be cast to org.jbpm.process.core.ContextContainer

Initially support for boundary events was only for state nodes - those that can stop in certain node. This was mainly for the catch events like signal or message - as if the node is not going to stop and just run through like script task there is no way to send a signal to it. Though error events are bit different and thus makes sense to have them supported.

Please add the new feature that the business rule task could support the boundary error event in a workflow process.