Hello Mark et all,
I referred the source of the class (FOr API etc) of the built-in evaluator below :
org.drools.core.base.evaluators.MatchesEvaluatorsDefinitionand
drools.packagebuilder.confdrools.evaluator.coincides = org.drools.core.base.evaluators.CoincidesEvaluatorDefinition
drools.evaluator.before = org.drools.core.base.evaluators.BeforeEvaluatorDefinition
drools.evaluator.after = org.drools.core.base.evaluators.AfterEvaluatorDefinition
drools.evaluator.meets = org.drools.core.base.evaluators.MeetsEvaluatorDefinition
It was a breeze, took me less than 10 minutes!
As Mark Proctor mentioned, lots of plumbing has been taken care of in 6.1 and actually this port was really nice and easy.
I was able to port my old
inlistoperator from Drools 5.3 to 6.1
Now I am willing to recommend my client to use Drools 6.x for our forth coming major initiative. We have a custom in-house built Rule Engine which I am trying to replace with Drools. The "Custom Evaluator" is a major thing for as as all its really powerful and all the analysts need this.
Without this
inlist<.b> operator I am not going anywhere with Drools with my client. We will be processing in excess of 30 million FACTS, (Stateless Session) using Drools when I am done converting the project to use Drools!
Thanks for all
Matt'M