Bug 1247913 - FireUntilHalt should throw UnsupportedOperationException when called from KieSession from RuntimeEngine
Summary: FireUntilHalt should throw UnsupportedOperationException when called from Kie...
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: BRE
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ER3
: 6.2.0
Assignee: Edson Tirelli
QA Contact: Tibor Zimanyi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-29 08:39 UTC by Tibor Zimanyi
Modified: 2020-03-27 20:05 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-03-27 20:05:58 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Tibor Zimanyi 2015-07-29 08:39:39 UTC
Description of problem: 

When fireUntilHalt is called from KieSession that is obtained from RuntimeEngine, no rules are fired. According to BZ [1], using fireUntilHalt in jBPM engine is not a valid use case, so it should throw UnsupportedOperationException or something similar, so the user is informed, that he should not use it. See [1] for more info. 

How reproducible: Run test from this paste [2]

Additional info:

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1218291
[2] http://pastebin.com/t40cS285

Comment 2 Maciej Swiderski 2015-09-08 12:49:13 UTC
it does work ok when using singleton runtime manager only as it does keep the ksession active so it can be used. enabled tests in jbpm-test-coverage that proves it and is same as linked in this bs

jbpm
master:
https://github.com/droolsjbpm/jbpm/commit/ab41cdee03b421d741775c0cdf0f15ca419eab8c

6.3.x:
https://github.com/droolsjbpm/jbpm/commit/2dcaf21d724d251e013870bc356eee509ef8c56e

Comment 3 Tibor Zimanyi 2015-10-07 11:49:18 UTC
Verified. The test passes. Is this somewhere documented? I think we should document this behavior if we don't have it documented yet (only singleton runtime manager when using fireUntilHalt).


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