[JBoss JIRA] Created: (JBRULES-2523) OSGI'fy Drools Guvnor
by Ravid Te (JIRA)
OSGI'fy Drools Guvnor
---------------------
Key: JBRULES-2523
URL: https://jira.jboss.org/browse/JBRULES-2523
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-guvnor
Affects Versions: 5.1.0.M1
Environment: OSGI environment
Reporter: Ravid Te
Assignee: Mark Proctor
Guvnor currently does not work inside an OSGI container without a lot of effort and work.
There seems to be lots of issues regarding SEAM in order to make a fully functional osgi'fyed guvnor.
I would like to request to drools developers to provide a working OSGI'fyed guvnor that folks in the community can use without the need for so many workarounds and the need for so many dependency resolutions.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (JBRULES-2482) Binding seems to be unreliable with MVEL dialect and mulitple evals
by Chris DeLashmutt (JIRA)
Binding seems to be unreliable with MVEL dialect and mulitple evals
-------------------------------------------------------------------
Key: JBRULES-2482
URL: https://jira.jboss.org/jira/browse/JBRULES-2482
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core (expert)
Affects Versions: 5.1.0.M1
Environment: Windows 7, Sun JDK 1.6.0_17
Reporter: Chris DeLashmutt
Assignee: Mark Proctor
When using the MVEL dialect, a rule with multiple binds, and a chain of evals, the bindings seem to be incorrect.
For example here is some DRL:
rule "Modify Field Rule for Form: InterrelatedFieldsTestForm.fieldA (Set fieldA optional if values are in other fields)"
when
$fieldA: Field(id == "fieldA")
$fieldB: Field(id == "fieldB")
$fieldC: Field(id == "fieldC")
(eval(ValidationFunctions.isChecked($fieldA)) or eval(ValidationFunctions.isChecked($fieldB)) or eval(!ValidationFunctions.isBlank($fieldC)))
then
ValidationFunctions.insertOperation(fieldOperations, new FieldOperation("fieldA",FieldOperation.OPTIONAL));
end
If I put debugging statements in to the static ValidationFunctions methods, or if I put breakpoints in those same static methods, I see invocations using bound variables that don't match what I declared.
For instance, I'll see isBlank called with what appears to be the contents of $fieldA.
If I combine the evals into a single eval with each condition separated by ||. everything seems to function properly. I can't easily go back and change the syntax in my exisiting rules however, and the syntax I'm using seems to be valid based on my interpretation of the documentation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month