well said dave (I am going to copy and paste that into the documentation right now) ! Throughout the history of rule engines, executing actions is considered almost as an afterthought, interesting.....
Yeah we have only just started looking at how we can work with jBPM, but I know some folks have been looking at providing integration with it, which would be a nice overall package for some as they can more from BPM to rules and back easily, using the best tool for the job. HOWEVER, I can appreciate the power of being able to have arbitrary snippets of code, and manage them in a database. I have lived in worlds where it can take 3 months or more to get a small change to anything "software" to production, yet "data" can be migrated overnight (or weekly at worst). Having code as data is a great and old concept (and none too easy in java, alas ! I guess thats part of the reason why things like drools get popular in the first place, partly to work around java's limitation). bug debug tools are on the way... we have the start of them for inspecting WM and agenda contents. I can see putting a breakpoint on a rule a next step. On 4/20/06, Hamu, Dave <[EMAIL PROTECTED]> wrote: > > Interesting comment Michael. JBoss has the concept of the JBoss JEMS or > Enterprise Middleware Stack which layers Rules, Workflow and Business > Process Execution. It seems to me that in the excitement of working > with rules engines, that people forget that a rules engine is only one > piece of a complex application or solution. Rules engines are not > really intended to handle workflow or process executions nor are > workflow engines or process management tools designed to do rules. Use > the right tool for the job. Sure, a pair of pliers can be used as a > hammering tool in a pinch, but that's not what it's designed for. > > - Dave > > > -----Original Message----- > From: Michael Neale [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 19, 2006 9:35 PM > To: [email protected] > Subject: Re: [drools-user] Break points in rules for 3.0 ? > > not yet no... > but within the consequences, and functions, would be nice. Unfortunately > it is non trivial to do, even with eclipse, but it can still happen. We > really want to (optionally) treat the RHS as a chunk of java code. > We may be able to do this sooner though as we do know the line number > (the offset to the rule), but it will not be as thorough as the JDT. > > I guess if the code in the RHS is that complicated, I would want to move > it out into regular classes and so on... as its moving away from rules > and toward code. For better or worse, people see drools as a way to do > java code dynamically, but thats not really the whole story ! I have > been there, and I know how much easier it is to make changes when stuff > is embedded in a rule, but its dangerous and powerful. > > > > On 4/20/06, Ho, Alan <[EMAIL PROTECTED]> wrote: > > > > Would it be possible to have break points in DRL files ? I'm > > particularly interested in having break points within the consequence > > section of the code. > > > > One of the great things about having rules in Java is the ability to > > use breakpoints, the debugger, etc. > > > > Regards, > > Alan Ho > > > > >
