Re: [rules-users] "Not" Non-Existential Quantifier

2008-08-04 Thread ringsah
Edson, I finally succeeded in coming up with a simple test case that shows the problem. I have attached the necessary files, which include a test case, three fact objects, and the drl. One key to this test are the fact that the Applicant fact object has an "equals" method that tests for equali

RE: [rules-users] "Not" Non-Existential Quantifier

2008-08-04 Thread Fenderbosch, Eric
How is your rule base configured, with identity or equality assert behavior? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, August 04, 2008 9:59 AM To: Rules Users List Subject: Re: [rules-users] "Not" Non-Existentia

RE: [rules-users] "Not" Non-Existential Quantifier

2008-08-04 Thread ringsah
The default - identity. -- Original message -- From: "Fenderbosch, Eric" <[EMAIL PROTECTED]> How is your rule base configured, with identity or equality assert behavior? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, Au

Re: [rules-users] "Not" Non-Existential Quantifier

2008-08-04 Thread Edson Tirelli
Oh, I see. Unfortunately in this case, there is nothing we can do about it, because the rules are behaving exactly as they were supposed to behave: NegativeResult(applicant == $applicant) As you can see, they are telling the application to use the equals comparison in the constraint: a

Re: [rules-users] "Not" Non-Existential Quantifier

2008-08-04 Thread Edson Tirelli
Eric, Unfortunately, in his case does not matter if he is using identity or equality behavior, because the problem is in the constraint, that is telling the engine to use equals(): applicant == $applicant []s Edson 2008/8/4 Fenderbosch, Eric <[EMAIL PROTECTED]> > How is your r

Re: [rules-users] "Not" Non-Existential Quantifier

2008-08-04 Thread ringsah
Okay, I understand now. I had incorrectly assumed that the "applicant == $applicant" constraint was using identity. Not a big deal to work around. It seems like you would most often want to use identity in constraints, but I guess you have to provide for those cases when you need to use equality

[rules-users] Re.Problems with looping

2008-08-04 Thread thomas kukofka
*Hello, I tried this but it still loops: public boolean equals(Object o) { if(o instanceof OutputObject) { OutputObject other = (OutputObject)o; if (this.type != other.type) { return false; } if (this.type == OutputObjec

[rules-users] Drools win BRMS Bossie

2008-08-04 Thread Mark Proctor
Drools has won an infoworld Bossie award for best open source BRMS : http://www.infoworld.com/slideshow/2008/08/166-best_of_open_so-6.html ___ rules-users mailing list rules-users@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users