Bug 1328687 - [RFE] business rule task supports boundary error event
Summary: [RFE] business rule task supports boundary error event
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Core
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Alessandro Lazarotti
QA Contact: Radovan Synek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-20 04:13 UTC by Gary Hu
Modified: 2020-03-27 20:13 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 20:13:20 UTC
Type: Feature Request
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.