Hi Andy Mei,
In your DSL file you put some parentheses. I think it's the problem. Try
with this :
[when]There is a person with=person:Person()
[when]-age is at least {age} years old=age = {age}
[when]-age is less than {age} years old=age {age}
[when]-must has a name=name != name != null
Hi list,
I have developed a web service for deploy my rule package, this rule
package is in the BRMS, the source code of the web service class is:
public class ValidaLlamadaWS {
RuleAgent agent =
RuleAgent.newRuleAgent(/brmsdeployedrules.properties);
RuleBase ruleBase =
Hello all,
I am working on the excel driven rules application and have a small query. The
app is for a mobile service provider. The following are the requirements.
The company has 3 plans(apart from a default plan) which a user can opt from
while taking the connection. However if the user does
I have a use case where we'd like to match free text strings, with words
sometimes spelled incorrectly. Has anyone tried Drools with an approximate
string matcher (http://en.wikipedia.org/wiki/Approximate_string_matching)?
I know that I can use regular expressions to match some common spelling
Well the sheet can do with deciding the plan - in code if none is decided
then the default one applies (ie the default is not part of the rules).
As for the rest - well think of columns as fields and rows as rules, and you
will get the idea with some practice.
On 9/4/07, Rajeev Dave [EMAIL
Hi Irving. That is a very interesting and kind of cool problem.
Happily, Mike Brock who built MVEL, which is part of drools, embeded soundex
into it.
So you can do (and I just tried this):
rule Hello World
when
c : Cheese( eval(type soundslike foobar) )
then
Also, there is strsim: http://mvel.codehaus.org/String+Similarity+Check
so you can do
Something( eval( (field strsim blah) 0.9 ) )
(or something like that anyway - to look for similarity rating). But I think
soundex is what you really want.
On 9/4/07, Michael Neale [EMAIL PROTECTED] wrote:
Hi Edgardo.
Well it shouldn't leak like that.
Looking at your code, I am not sure how it works (as I am not sure of the
Web Service component you are using).
But if the web service is creating a new instance of the ValidaLlamadaWS
class for EACH call, then yes that woudl be the problem. What
If it still happens - it would be good if you could attach some code to
reproduce it to a JIRA.
On 9/4/07, Michael Neale [EMAIL PROTECTED] wrote:
Hi Edgardo.
Well it shouldn't leak like that.
Looking at your code, I am not sure how it works (as I am not sure of the
Web Service component
