Hide Forgot
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000004ReCC&sfdc.override=1 securitylevel_name: Public Platform JIRA for [JBRULES-2872] NPE in AbstractCompositeRestriction when using unbound variables
Link: Added: This issue incorporates JBRULES-2872
Triaged by the BRMS PM team for 5.2.
As per comments on JBRULES-2872, I was unable to reproduce the NPE, but fixed line numbers on error messages. Commit: https://github.com/droolsjbpm/drools/commit/0c025c90adb0751bdb7622faa2ed9c82190ba587
I was able to reproduce NPE in BRMS 5.1.0 with following code: package com.sample import org.drools.verifier.components.NumberRestriction rule "x" when NumberRestriction( valueType == Field.INT || == Field.DOUBLE ) then end I have tested it in BRMS 5.2.0 ER3 and it is fixed.
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: https://bugzilla.redhat.com/show_bug.cgi?id=724655 A NullPointerException was occurring in AbstractCompositeRestriction when using unbound variables were used, however this was a side effect of missing import statements. The bug has been corrected and no longer presents.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,3 +1 @@ -https://bugzilla.redhat.com/show_bug.cgi?id=724655 - A NullPointerException was occurring in AbstractCompositeRestriction when using unbound variables were used, however this was a side effect of missing import statements. The bug has been corrected and no longer presents.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -A NullPointerException was occurring in AbstractCompositeRestriction when using unbound variables were used, however this was a side effect of missing import statements. The bug has been corrected and no longer presents.+A NullPointerException was occurring in AbstractCompositeRestriction when using unbound variables as a side effect of missing import statements.