Subject: [drools-user] Drools GUI??? - msg#00102

Previous Message by Date: click to view message preview

Re: [drools-user] events and durations

ActivationFired we can keep, just Created and Cancelled I'm looking to drop. Mark Cacciatore, Kyle (Contractor) wrote: I do. However, I am new to drools and rule engines in general, so there may be a better way to implement what I am doing that I'm not aware of. Given a set of rules, I want to stop evaluating as soon as a rule evaluates to true. The consequence for each rule is to queue an object (for processing by another component), and retract the asserted object from the Working Memory. The end of the consequence fires an ActivationFired event, which the other component listens for, pops the object off the queue for further processing. Kyle -----Original Message----- From: Mark Proctor [mailto:mproctor@xxxxxxxxxxxx] Sent: Friday, January 28, 2005 11:16 AM To: dev@xxxxxxxxxxxxxxxxxxx; user@xxxxxxxxxxxxxxxxxxx Subject: [drools-user] events and durations Does anyone here use, or think they will use, ActivationCreated and ActivationFired events? We are profiling and the current modifyObject method, where we try and retract only the no longer matching activations, is sub-optimal due to exponential iterations. We have looked into other systems and it seems they do a simple retract and assert. We would like to do the same but it means we loose the two events, keeping them inroduces considerable overhead - so my proposal is to remove them. The issue is that on a modify, where we did a retract and assert, we would have no idea whether a retract would be put back on again and thus no idea whether we should fire an ActivationCancelled event. This problem also affects duration, which uses java.util.Timer, where the timer is reset on the retract and asssert. I'm trying to find some compromise as I would like to keep the feature - but if no one is using it or thinks they will use it I may disable it for the near future which will speed up the 2.0 release. Regards Mark

Next Message by Date: click to view message preview

Re: [drools-user] Combining logical expressions

Bob McWhirter wrote: Shouldn't use OR's just so you can avoid specifying the same consequence multiple times. ... Ok, that makes sense. Thanks. -- barry kaplan groups1@xxxxxxxxxxx

Previous Message by Thread: click to view message preview

[drools-user] events and durations

Does anyone here use, or think they will use, ActivationCreated and ActivationFired events? We are profiling and the current modifyObject method, where we try and retract only the no longer matching activations, is sub-optimal due to exponential iterations. We have looked into other systems and it seems they do a simple retract and assert. We would like to do the same but it means we loose the two events, keeping them inroduces considerable overhead - so my proposal is to remove them. The issue is that on a modify, where we did a retract and assert, we would have no idea whether a retract would be put back on again and thus no idea whether we should fire an ActivationCancelled event. This problem also affects duration, which uses java.util.Timer, where the timer is reset on the retract and asssert. I'm trying to find some compromise as I would like to keep the feature - but if no one is using it or thinks they will use it I may disable it for the near future which will speed up the 2.0 release. Regards Mark

Next Message by Thread: click to view message preview

Re: [drools-user] Drools GUI???

Yes once I 2.0 I will be making an effort in that direction - I have already been looking at a debugger that works with janino for eclipse. Mark Hamu, Dave wrote: Friends, The more rules engines that I look at, the more that I am impressed with Drools. Is there a project envisioned to create a GUI for Drools for rule construction? What I am thinking of is something that would allow a user to do the following things: 1) To define and organize rule repositories, rule projects, rulesets, rules and rule versions 2) Use Reflection to browse classes for creating inclusions in the DRL. 3) To provide a means of defining various rule patterns for constructing types of rules or rule sets that have known behavior and can be used as templates for constructing more involved rulesets 4) To provide a place for syntax validation whether for JAVA, PYTHON or GROOVY drl. 5) Something that could ultimately include some graphical metaphor for rule organization whether it be diagramatic or treeview based. 6) Something that could be extensible to support Domain Specific Language. Any thoughts on this? Dave Hamu