Bug 754893 - Parser doesn't accept mvel BigInteger and BigDecimal literals in LHS
Summary: Parser doesn't accept mvel BigInteger and BigDecimal literals in LHS
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: BRE (Expert, Fusion)
Version: BRMS 5.2.0.GA
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: BRMS 5.3.0.GA
Assignee: Nobody
QA Contact: Marek Baluch
URL:
Whiteboard:
Depends On:
Blocks: 754895
TreeView+ depends on / blocked
 
Reported: 2011-11-18 05:12 UTC by Toshiya Kobayashi
Modified: 2022-08-12 04:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
JBoss BRMS 5.3 did not have support for BigDecimal and BigInteger literals causing an error when Fact values were of BigDecimal or BigInteger type. Support has been added for BigDecimal and BigInteger types and this issue no longer occurs.
Clone Of:
Environment:
Last Closed:
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 754895 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Issue Tracker JBRULES-3292 0 Major Closed Parser doesn't accept mvel BigInteger and BigDecimal literals in LHS 2012-08-29 05:45:00 UTC

Internal Links: 754895

Description Toshiya Kobayashi 2011-11-18 05:12:17 UTC 
Platform BZ for JBRULES-3292.
It prevents customers from migrating rules from older version.
Comment 1 Edson Tirelli 2011-11-22 03:28:59 UTC 
Fix applied to branches 5.2.x, 5.3.x and master (5.4).
Comment 2 Jiri Svitak 2012-01-02 15:31:47 UTC 
Parser now accepts mvel BigInteger and BigDecimal literals. Verified in BRMS 5.3.0 ER1.
Comment 6 lcarlon 2012-06-06 00:11:59 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
JBoss BRMS 5.3 did not have support for BigDecimal and BigInteger literals causing an error when Fact values were of BigDecimal or BigInteger type. Support has been added for BigDecimal and BigInteger types and this issue no longer occurs.
Note You need to log in before you can comment on or make changes to this bug.