[rules-users] Coding up an "intersects" operator

Dirk Bergstrom dirk at juniper.net
Mon Feb 4 13:56:39 EST 2008


Edson Tirelli was heard to exclaim, On 02/04/08 04:22:
>    If you are using trunk, look at the interface EvaluatorDefinition as
> your entry point. All you need to do is to create an implementation for
> it. This is part of the pluggable evaluators framework I'm working on.

That sounds like the way to go.  Do you think trunk (or at least this feature)
will be stable enough to use by the end of the month?  I'm brave...

> The only part that is not pluggable yet is the parser, but once you are
> done with your implementation, I can fix the parser for you in a couple
> minutes.
>    Join the IRC and talk to me and I can guide you.

Thanks.  I'll show up later this week, after I get the current round of features
rolled out.

>    If you are using older versions of Drools (not trunk) things will be
> a lot more complicated. :(

I don't like complicated.

> 2008/2/4, Dirk Bergstrom <dirk at juniper.net <mailto:dirk at juniper.net>>:
> 
>     It looks like I'm going to need to implement the "intersects"
>     operator for a
>     project I'm working on.  As in "Does this collection share at least
>     one element
>     with that collection".
> 
>     Unfortunately, I'm going to need it in about two weeks.  Too bad I
>     didn't plan
>     ahead...
> 
>     So, if anyone can send me some pointers on where in the code I should be
>     looking, I'd be very grateful.  I don't think it will be
>     particularly difficult
>     to write the actual code, but I'm worried that I'll never be able to
>     figure out
>     all the places in the codebase that I have to touch.
> 
>     A ways back, Edson said that I could use the work on "contains" as a
>     model; is
>     there a single subversion commit that lists all the files affected
>     by that?


-- 
Dirk Bergstrom               dirk at juniper.net
_____________________________________________
Juniper Networks Inc.,          Computer Geek
Tel: 408.745.3182           Fax: 408.745.8905



More information about the rules-users mailing list