Hello, It seems that the logic behind the "operator" drop-down list comes from the "org.drools.ide.common.client.modeldriven.SuggestionCompletionEngine" and "org.drools.eclipse.rulebuilder.modeldriven.HumanReadable" classes. That's for the "rule authoring" perspective. I've also seen that the business rule editor involves the DrlParser class. So, in a "rule parsing" perspective, I guess I need to find a way to register my custom operator into the EvaluatorRegistry used by the Eclipse plugin (and I don't know where this can be done).
Do you think I am on the right track? Is there a risk that code modifications will involve so many classes that, in the end, adding a custom operator to the business rule editor will be a difficult task for someone very new to Drools (like me)? Thanks in advance, Best regards, Bruno. Bruno Freudensprung a écrit : > Hello, > > I'd like to implement a custom "lucenematches" operator that would > enable writing conditions like: > $d : Doc(text lucenematches "(foo AND bar) OR roam~0.8") > > As I've taken a look at the following post on athico > (http://blog.athico.com/2009/05/imperfect-evaluations.html), and seen > that the appendix B of the "Drools JBoss Rules 5.0 Developer's Guide" > book that deals with custom operators, I am rather confident that I will > find my way in implementing my operator (if not, I'll post here again :-)). > > However, I wonder if it will be possible to add my "lucenematches" > operator to the "operator" drop-down list of the Eclipse's Business Rule > Editor. > Does anyone have an idea? > > Best regards, > > Bruno. > _______________________________________________ > rules-users mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/rules-users > > _______________________________________________ rules-users mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-users
