Tomcat 6.0 + BRMS
by Sergio Lombrico
Hi. Has anyone manged to get the BRMS running with Tomcat 6.0 ?
I have followed the instructions:
"If you are using Tomcat 5,6 or any other application server different than
JBoss AS 4.x
please follow this
instructions<http://wiki.jboss.org/wiki/Wiki.jsp?page=JBRMSjsfdependencies>to
get BRMS working in your environmen"
but cannot manage to get the BRMS to start.
Has anyone had success with this ?
Sergio
17 years, 2 months
drools 5.0 quotes
by Mark Proctor
We are just updating the website for the 5.0 launch. I'm looking for
anyone that works for a well known firm who would be willing to give us
a quote (just one or two lines), particularly around Drools Flow or
Fusion. This is not a testimoney or a reference. It's just a quote on
what you think, the promise of the technology, or how you hope it'll
help your business - something along those lines. If you can help,
please contact me directly. Ideally we'd like two or three quotes to go
out with the release announcement.
Thanks
Mark
17 years, 2 months
Tomcat 6.0 + BRMS
by john.shepherdson＠bt.com
I got the Guvnor component of Drool 5M5 working with Tomcat 6.0 by doing
the following (but it doesn't seem to work for Drools 5CR1):
Remove tomcat-6.x\webapps\drools-guvnor\WEB-INF\lib\el-api-x.jar
Remove existing tomcat-6.x\lib\jsf-api.jar and jsf-impl.jar
Replace with contents of jboss_jsf_libs.zip
(downloaded from
http://download.jboss.org/drools/dependencies/jboss_jsf_libs.zip)
Edit 'repositoryConfiguration' in
webapps\drools-guvnor\WEB-INF\components.xml to point to a directory
that exists
John S
17 years, 2 months
Guvnor's Scenario returning "Error rebuilding RuleBase"
by Ingold, Jonathan
Hello,
I am receiving an "Error rebuilding RuleBase" error in Guvnor anytime I
run a scenario against rules that reference a constant. Also the
constants are not available in the scenario tool.
An example of a rule that I have used that references a constant would
be:
***********************************************
rule "First"
salience 10
when
$a : Action(task == ConstantC.UNO)
then
System.out.println("First Rule Fired");
end
*************************************************
Note "task" is a ConstantC object.
The constant UNO is declared in my java class with the line:
*******************************************************************
public static ConstantC UNO = new ConstantC(1, "One");
********************************************************************
The rule fires perfectly in Eclipse with the expected result. Could
this possibly be a bug with Guvnor? I couldn't find anything in JIRA
relating to this.
Any input is appreciated!
Thanks,
Jon
17 years, 2 months
Integrated User Configurable Rules Templates and DSL Example
by Tim Langford
Hello All,
I am very new to Drools and thinking about using it in a project.
Apologies if these questions are naive - I have read the excellent
documentation and written and run some examples but am still feeling a
little lost.
Due to the nature of the existing system the project will depend on we
want to utilize the engine such that it operates and behaves like a
'function':
1) The system will always assert a single hierarchical object into the
working memory of the required type.
2) Global variables will be attached to the working memory to provide
visibility of system objects ; and also defined a set of return
objects (to be retrieved by the host system after execution.
3) The rules will be execute to produce a set of results that will
then be acted on externally by the host system.
For example:
We assert a 'Journey' (or another object) into a working memory with
the following rule:
rule "Journey No Charge Cancellation Option"
dialect "java"
when
# There are at least "{days}" days before the journey begins
$journey : Journey( )
eval(daysToDeparture($itinerary) > 30)
then
>toDebugLog("Journey 'no charge' cancellation.", logger);
>CancelOption option =
instanceOfCancellationOption(kcontext.getRule().getName(),
"CancelProcessor", 0);
>cancelOptions.add(option);
end
function CancelOption instanceOfCancellationOption(
String ruleName,
String targetProcessor,
Integer percentageBasedCharge) {
CancelOption option = new CancelOption();
option.setInvokingRule(ruleName);
option.setTargetProcessor(targetProcessor);
option.setDepositBasedChargePercentage(percentageBasedCharge);
return option;
}
The system must support different users from different companies - so
these rules need to be 'templated'. We need to allow users to define
their own instances and constraints on any of the template rules
defined. Furthermore, they maybe from different countries so system
must use the DSL functionality to wrap the rules and parameters in
something meaningfully to them. Finally, we need to be to be able add
constraints over the rules to ensure users do not misconfigure the
rules and rules values (for example only a set of date ranges for
canceling a journey that don't overlap). We don't want to use the
spreadsheet templating mechanism. Rule configuration will have to be
provided in our weblication (and backed by the guvnor).
I could easily achieve this in pure java, groovy, etc. but would like
to condsider drools due to 1) Wanting it to be a bit more dynamic than
java (whilst not being so dynamic a user can easily make a mistake or
get confused); 2) Getting the DSL features; 3) taking advantage of the
all the rule versioning and management performed by the RMS.
Sorry for the long introduction. My questions are:
1) Is Drools an overkill such functionality? (I am no expert).
2) Is there an example that uses templating (without spreadsheets) and
DSL's somewhere? Does this work with the 'guvnor'? I have tested most
Drools functionality, but don't seem to be able to get a handle on
using all together to achieve this goal.
Any insight or recommendations will be greatully recieved.
Thanks
Tim
17 years, 2 months
Drools-4.0.7 + OC4J
by Vir
Hi all,
I am new to drools. I am facing a very strange issue while working with
JDeveloper + OC4J 10 + Drools 4.0.7. If I execute my "hello world" program
in "debug" mode of JDeveloper then all my rules are working properly. But
when I execute it in "run" mode then execution stops at following line
builder.addPackageFromDrl(new
InputStreamReader(CreditExample.class.getResourceAsStream("/abc.drl")));
Also there is no exception thrown. I don't know what is the problem at
run time. Can anyone please help me out
Thanks
Vir
--
View this message in context: http://www.nabble.com/Drools-4.0.7-%2B-OC4J-tp23190680p23190680.html
Sent from the drools - user mailing list archive at Nabble.com.
17 years, 2 months
"==" operator does not work on float and double type
by Zeke
Hi, All:
My drl file is like below:
package org.drools.examples;
import org.drools.examples.HelloWorldExample.Message;
rule "check deep int"
dialect "java"
when
m:Message( sec.fir.d == "99.9" )
then
System.out.println( "===check deep double ok===" );
end
I find that "==" operator does not work well on double and float type.
This condition can not be satisfied. If I change the condition to sec.fir.d
< "100" or sec.fir.d > "99.8", it works well. Is it a bug?
I attach my test code. And I add below jars into classpath:
antlr-runtime-3.0.jar
core-3.2.3.v_686_R32x.jar
drools-compiler-4.0.7.jar
drools-core-4.0.7.jar
drools-decisiontables-4.0.7.jar
drools-jsr94-4.0.7.jar
janino-2.5.10.jar
jsr94-1.1.jar
mvel-1.3.12-java1.5.0.jar
Can anyone kindly help me?
Thanks!
- Zeke
17 years, 2 months
When-becomes-true semantics
by Allan Terry
I am looking for the following semantics:
Lets say I have a Boiler class with location, temperature, and pressure
fields.
I write a rule like When Boiler(temperature > 240) then ....
I want the rule to trigger when its condition becomes true, not when it
is true in all cases. I don't want it to trigger again if the facts
change but the condition is still true. The actions may have adverse
consequences if fired too freely.
Example:
Event with temperature set to 250. Rule should fire
Another event for the same boiler with temperature = 270. Rule is still
true, should not fire
Now set its temperature to 100. Rule should not fire
Set temperature to 260. It has become true again and should fire.
Multiple clauses should not change things. When the entire condition
becomes true, the action is activated. The facts tested in the various
clauses will vary with time, but as long as the condition remains true,
the action should not be triggered with each change.
I tried this with one class and one event which I repeatedly modified.
It fires when a new value satisfies the condition, whether or
not it was true before.
Interestingly, this worked for classes with a single field, but as soon
as I added multiple fields I started getting the "is true" semantics.
If that isn't native semantics for RETE, is there a reasonable approach I
could take to layer it on, considering I want all my rules to act this way?
thanks, Allan
17 years, 2 months
