Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1227234 - Regression in "forall" operator in Decision Tables
Regression in "forall" operator in Decision Tables
Status: VERIFIED
Product: JBoss BRMS Platform 6
Classification: Retired
Component: BRE (Show other bugs)
6.1.0
Unspecified Unspecified
unspecified Severity unspecified
: DR1
: 6.2.0
Assigned To: manstis
Marek Winkler
:
Depends On:
Blocks: 1228050
  Show dependency treegraph
 
Reported: 2015-06-02 04:33 EDT by Anton Giertli
Modified: 2015-10-14 03:46 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1228050 (view as bug list)
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
[0] reproducer (14.83 KB, application/zip)
2015-06-02 04:33 EDT, Anton Giertli
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker DROOLS-802 Major Resolved Quotes are mistakenly removed from cell value with 'forall' constraints 2016-05-23 07:06 EDT

  None (edit)
Description Anton Giertli 2015-06-02 04:33:18 EDT
Created attachment 1033662 [details]
[0] reproducer

Description of problem:
The forall operator used in decision table will not get compiled into a kjar successfully.

This worked in jBPM 6.1.0.Final and fails with BPMS 6.1 (which is based on jBPM 6.2.0)

Version-Release number of selected component (if applicable):
BxMS 6.1

How reproducible:
always

Steps to Reproduce:
1. Run the reproducer with OLD jbpm - it gets compiled
2. Run the reproducer with NEW jBPM - it will NOT get compiled
3.

Actual results:

Decision table including forall operator is not compilable

Expected results:
Decision table including forall operator is compilable

This issue may be caused by
https://github.com/droolsjbpm/drools/commit/c37653ae479e87802b288e3d57babcea6d84ac36#diff-f999821fae00a73ec4b62d21d1b7559dR172

Additional info:
Comment 3 JBoss JIRA Server 2015-06-02 05:23:07 EDT
Mario Fusco <mario.fusco@gmail.com> updated the status of jira DROOLS-802 to Resolved
Comment 4 Mario Fusco 2015-06-02 05:23:38 EDT
Fixed by https://github.com/droolsjbpm/drools/commit/52fa55316
Comment 5 Marek Winkler 2015-10-14 03:46:42 EDT
Verified in BRMS 6.2.0 ER3 by running both the provided reproducer and the unit test included with the fix.

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