Bug 1227234 - Regression in "forall" operator in Decision Tables
Summary: Regression in "forall" operator in Decision Tables
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: BRE
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: DR1
: 6.2.0
Assignee: manstis
QA Contact: Marek Winkler
URL:
Whiteboard:
Depends On:
Blocks: 1228050
TreeView+ depends on / blocked
 
Reported: 2015-06-02 08:33 UTC by Anton Giertli
Modified: 2020-03-27 20:13 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1228050 (view as bug list)
Environment:
Last Closed: 2020-03-27 20:13:57 UTC
Type: Bug
Embargoed:


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


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker DROOLS-802 0 Major Resolved Quotes are mistakenly removed from cell value with 'forall' constraints 2016-05-23 11:06:15 UTC

Description Anton Giertli 2015-06-02 08:33:18 UTC
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 09:23:07 UTC
Mario Fusco <mario.fusco> updated the status of jira DROOLS-802 to Resolved

Comment 4 Mario Fusco 2015-06-02 09:23:38 UTC
Fixed by https://github.com/droolsjbpm/drools/commit/52fa55316

Comment 5 Marek Winkler 2015-10-14 07:46:42 UTC
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.