Bug 1175689 - Default handler for BoundaryErrorEvent to meet BPMN2 spec
Summary: Default handler for BoundaryErrorEvent to meet BPMN2 spec
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Core
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER4
: 6.1.0
Assignee: Alessandro Lazarotti
QA Contact: Jozef Marko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-18 11:58 UTC by Toshiya Kobayashi
Modified: 2020-03-27 20:10 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-03-27 20:10:37 UTC
Type: Enhancement
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBPM-4527 0 Major Resolved Default handler for BoundaryErrorEvent to meet BPMN2 spec 2016-08-01 07:20:39 UTC

Description Toshiya Kobayashi 2014-12-18 11:58:39 UTC
Description of problem:

Platform BZ for https://issues.jboss.org/browse/JBPM-4527

There is a workaround (no structureRef) in BPMS 6.0.x. But in master/6.2.x, there doesn't seem to be a workaround ('no structureRef' is not effective since https://github.com/droolsjbpm/jbpm/commit/08877c1a)

Steps to Reproduce:
1. See pull requests in JBPM-4527

Actual results:

BroundaryErrorEvent doesn't become a default handler when <error> doesn't have errorCode.

Actually, 2 unit tests (testBoundaryErrorEventDefaultHandlerWithoutErrorCodeWithStructureRef/testBoundaryErrorEventDefaultHandlerWithoutErrorCodeWithoutStructureRef) in JBPM-4527 fails with a different reason (XmlBPMNProcessDumper.dump()) at this moment. But you can test those bpmn2 files with a usual jBPM program.

Expected results:

BroundaryErrorEvent becomes a default handler when <error> doesn't have errorCode.

Comment 1 Maciej Swiderski 2014-12-18 17:23:59 UTC
fixed according to bpmn2 spec and verified by test cases provided by Toshiya

jbpm
master:
https://github.com/droolsjbpm/jbpm/commit/6ec18beeecd89fcdfe2a247f089b9da94f88975f

6.2.x:
https://github.com/droolsjbpm/jbpm/commit/f35576b8c8a691d61d5f40f371e6010e9d8d6b49

Comment 2 JBoss JIRA Server 2014-12-18 17:25:33 UTC
Maciej Swiderski <swiderski.maciej> updated the status of jira JBPM-4527 to Resolved

Comment 4 Jozef Marko 2015-01-23 14:16:38 UTC
Verified in:
BPM Suite 6.1.0.ER4.


Note You need to log in before you can comment on or make changes to this bug.