We recently upgrade our Drools Expert from 5.1 to 5.3, expecting big
performance gain. But from the tests we done so far, the result is mixed at
best. Is this common or there is sth we can fine-tune the system?
http://drools.46999.n3.nabble.com/file/n3846747/PerformanceResult.png
All time is in
We are upgrading from Drools 5.1 to 5.3.0.Final, and running into issues with
loading precompiled rule/ruleflow files.
Previously, we precompiled our drl files using ant task
"org.drools.contrib.DroolsCompilerAntTask", e.g. rule1.drl to
rule1.drl.rules. We did the similar thing for ruleflow files,
Thanks for your reply. We do use "mvel".
I found out that we have to change our signature in JAVA from
methodA(String...) to methodA(String[])
and call it in rule like this:
bjA.methodA(new String[]{"string1"});
then it worked.
--
View this message in context:
http://drools.46999.n3.nabble.c
We are upgrading Drools from 5.1 to 5.3, and running into some issue when
invoking a Java method with
String variable arguments:
methodA(String... params)
how do we invoke this in a drl file? We used to call it in 5.1 as:
objA.methodA({"string1"});
and it works fine. Now in 5.3, it complains t
I found the issue: I have to set all the globals before inserting any facts:
cmds.add(CommandFactory.newSetGlobal( "addressManager", addressManager,
true));
...
cmds.add(CommandFactory.newInsert(event));
--
View this message in context:
http://drools.46999.n3.nabble.com/MVEL-Expression-causin
The NPE was caused by the call:
cmds.add(CommandFactory.newSetGlobal( "addressManager", addressManager,
true));
cmds.add(CommandFactory.newSetGlobal("fieldOperations", new HashMap(), true));
the addressManager is not available via this call, but if I switched all
Global setting via non-command API
Hi,
We are upgrading from Drools 5.1 to 5.3 to improve the performance, but we
are hoping to keep our drl files intact. We were trying to use the old drl
files by setting "drools.dialect.mvel.strict=false", but somehow with this
setting we still got " unable to resolve method using strict-mode .."
The global (?) addressManager is initialized *before* inserting the fact. As
for findFirstAddressByTypeByPerson(), the exception is thrown before it's
invoked: the NPE is thrown as part of the MVEL optimizers.
--
View this message in context:
http://drools.46999.n3.nabble.com/MVEL-Expression-cau
Hi,
I kept getting NPE for the following MVEL express in Drools rule:
---
rule "my Rule"
ruleflow-group "myGroup"
no-loop true
when
not Field(id=="meetingNotes")
$student : Student()
$homeAddress : Address() from
addressManage
Hi,
I need to upgrade from Drools 5.1 to 5.3, but keep the original drl files
intact. So I have to disable the strict mode. I tried all the 3 solutions:
1. -Ddrools.dialect.mvel.strict=false
2. set the property in Spring
3. directly set in Java code
But still getting the error:
[Error: unable to
Also, as part of our build process, we used
org.drools.contrib.DroolsCompilerAntTask in our maven file to compiled all
.rf file into a single ruleflow.flow file , which in turn was added to our
RuleBase in the following fashion:
DroolsObjectInputStream ruleFlowStream = new
Dr
We are upgrading from 5.1 to 5.3 and we had some rule flow files with .rf
extension, but the new jBPM in 5.2 and after is creating bpmn files instead
for process.
Can we still use the old rf file? or we have to recreate them as bpmn file?
Thanks.
--
View this message in context:
http://drools
Mark, thanks for your answer.
I just added the following dependency:
org.jbpm
jbpm-flow
5.2.0.Final
but still getting the same error, where the "processRuntime" is null. Am I
missing sth else here?
--
View this message
We are upgrading Drools Core from 5.1.1 to 5.3.1 and stilling using the old
RuleBase API, but we got Null Pointer Exception when running rules:
-
Caused by: [Error: wm.startProcess($phase.id): null]
[Near : {... WorkingMemory wm = drools.getW }]
...
Caused by: java.lang.NullPoi
Hi,
We have a legacy Drools application using 5.1 and we are planning to upgrade
to 5.3. I have several questions:
1. Are org.drools.StatelessSession and RuleBase deprecated? and instead we
should use KnowledgeBase and StatelessKnowledgeSession?
2. In 5.1.1, we extend WorkingMemoryLogger(final Wo
15 matches
Mail list logo