Not easily at present. You can use Events to track what is happening on the engine, and there is some support for looking at the Agenda in the plug in.
But the focus on the tools for all those features is for Drools 3. Also, when you build a rulebase, the "snippets" are actually parsed and compiled at that point (not just before executing) so there is that layer of protection. On 2/7/06, Ephemeris Lappis <[EMAIL PROTECTED]> wrote: > > Hello. > > > > I've been looking at the Drool's site, and (Google too !) but I didn't > find > anything about such tools. > > > > The DRL files syntax is quite simple for some development expert : the XML > structure of the rule system is not complex at all, and the Java sections > (or other semantic language) are rather simple too. But two points are > critical for our customer and for us too. > > > > First, the overall form and syntax of the file should be checked as soon > as > possible. A part of the text is XML based and could be easily verified > with > a schema aware tool. But the condition and action sections, written in > Java, > make the rule file composite and need a multi-language editor that should > at > the same time offer contextual help and/or completion, and check the code > correctness, similarly to what tools like Eclipse do. > > > > Is there any tool of this kind ? > > > > The second question is about rule systems debugging. A full work process > can > and must be defined to manage rule files, there versions, there > qualification and regression tests, etc. This must be done according to > the > needs and tools of the enterprise. > > > > But how can we debug rules ? How can we trace the inference path and > interrupt it to check drools or business objects state ? Is there a tool > for > this ? > > > > Thanks in advance. > > > > -- > > Ephemeris Lappis > > > > >
