Hi Mark ,
If i were to use decision tables outside eclipse what are the list of
dependency jar i need to have in classpath?
..\lib\drools-ant-5.0.1.jar ;
..\lib\drools-api-5.0.1.jar ;
..\lib\drools-bam-5.0.1.jar ;.
.\lib\drools-clips-5.0.1.jar ;
..\lib\drools-compiler-5.0.1.jar ;
Another change that occurred in parallel with the upgrade was responsible
for the upgrade. MY apologies for the false alarm.
I am now seeing a problem with Unable to load dialect ...
JavaDialectConfiguration - it appears to be looking for the Eclipse JDT jar
file. However, I have never required
Hi Scott,
All I can say is I am glad to hear. :)
Regarding your eclipse problem, please check 2 things: Drools plugin now
supports multiple runtimes the same way that eclipse supports multiple JDKs.
So, go to windows-preferences-drools-installed runtime to configure that.
Also, make
Edson,
I wasn't clear. I am getting this dialect error when I run the app outside
Eclipse. It works great in Eclipse.
Scott
___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
Scott Reed wrote:
Edson,
I wasn't clear. I am getting this dialect error when I run the app
outside Eclipse. It works great in Eclipse.
If you are outside of eclipse, then you need a compiler - either Janino
or JDT, it's always been that way.
Mark
Scott
2009/5/29 Mark Proctor mproc...@codehaus.org
Scott Reed wrote:
Edson,
I wasn't clear. I am getting this dialect error when I run the app
outside Eclipse. It works great in Eclipse.
If you are outside of eclipse, then you need a compiler - either Janino or
JDT, it's always been that
I just upgraded our app from Drools 4 to 5 libraries. We just use the
rules engine with DRL. The performance of the engine on our rulebase is
unacceptably slow. I assume there is something we need to do to our
rules or the way we are configuring the engine to fix this. I don't see
anything in
During a few experiments I did with MVEL, I have found that 2.x
actually performs slower than 1.x in our case. Maybe that is a
starting point.
Scott, do you have the possibility to profile your application using
4.x and using 5.x? That should reveal the bottlenecks and I am sure
that
Scott Reed wrote:
I just upgraded our app from Drools 4 to 5 libraries. We just use the
rules engine with DRL. The performance of the engine on our rulebase
is unacceptably slow. I assume there is something we need to do to
our rules or the way we are configuring the engine to fix this. I
Scott,
As others already mentioned, your e-mail does not help much. We need to
know what is unacceptably slow. How much slower is that? 10%, 100%, 1000%?
Also, we need a description of your use case: what kind of rules do you use,
how many rules, how many facts, etc. Finally, we need a way
Edson,
I figured I must have missed some docs explaining changes required for
the upgrade. If I suspected this was an inherent problem with the 5.0
release I'd have supplied lots of info. I am inferring from the response
that there are no known issues with 5.0 upgrade so I'll do my own
Indeed, at this point we are not aware of any performance problems. Of
course all the features we added may add a bit of overhead, but in our tests
that was completely offset by the improvements we made. The elimination of
shadow facts by itself is a huge boost for use cases with lots of
Mark,
I'm sorry I was unable to participate in pre-release testing. I didn't
think we had an especially unusual application. It's under 100 rules
with some simple evals and moderate processing on the consequence side.
I'll try Ingomar's suggestion and get profiles and, if necessary, I'll
13 matches
Mail list logo
