Hide Forgot
Date of First Response: 2009-09-10 00:50:45 securitylevel_name: Public Say I have a class Job with a method isFinished() that returns boolean. Also in a process context, I have a variable "job" of the type "Job". In a constraint on a split node, the following happens: a) When the constraint is in mvel dialect, the code "((Job)job).finished" is correct. b) When the constraint is in Java dialect, the code "Job j = (Job)(context.getVariable("job"));" gets me the following compilation error: Process Compilation error : org.drools.lang.descr.ProcessDescr@48f675 [omitted] (27:1248) : context cannot be resolved The documentation of this is quite clear: "Code constraints are expressions that return a boolean value. They have access to the context variable. MVEL code constraints also have direct access to the variables." Therefore I think this is a bug.
Link: Added: This issue is related to JBRULES-1978
Fix in place.
For documenting this in the Release Notes, can you please confirm the following and fill in the missing information. Dot point explanations are fine: The CAUSE (what was actually broken) * CONSEQUENCES of the bug (how it impacts users.) * A Boolean value was not returned correctly when a constraint on a split node was written in Java. * Instead, a compilation error occurred. The FIX (what was changed to eliminate this bug) and * RESULTS of the fix (what now happens for users.) *
We are still awaiting the outstanding information for the Release Notes on this one. Please provide it as soon as possible. Thanks.
The CAUSE (what was actually broken) * variable resolution wasn't working as expected in code constraints CONSEQUENCES of the bug (how it impacts users.) * a compilation error occurred when using context or variables in code constraints The FIX (what was changed to eliminate this bug) and * automatically inject context, kcontext and process variables as known java parameters RESULTS of the fix (what now happens for users.) * code constraints now have direct access to process variables and kcontext
added to the 5.0.CP01 release notes as resolved: JBRULES-1978 A compilation error would occur when attempting to access context or process variables in code constraints. This was caused by variable resolution not working as expected. This issue has been fixed by automatically injecting context, kcontext, and process variables as known Java parameters so that code constraints now have direct access to process variables and kcontext.