I have had a look at this tool. It seems to be interesting, but I'm afraid it is not an open-source software ! No more free alternative ? Thanks anyway.
-- Ephemeris Lappis > -----Message d'origine----- > De : ??? [mailto:[EMAIL PROTECTED] > Envoyé : mardi 7 février 2006 01:20 > À : [email protected] > Objet : ??: [drools-user] [Drools] Authoring and debugging tools > > > Maybe the DRLAssistant can help u to build and debug the DRL rule file. > U can find more details in this website: > http://www.zymose.com/ > > Now this eclipse plugin can surport only Drools2.1. > > -----邮件原件----- > 发件人: Ephemeris Lappis [mailto:[EMAIL PROTECTED] > 发送时间: 2006年2月6日 23:53 > 收件人: Drools users > 主题: [drools-user] [Drools] Authoring and debugging tools > > 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 > > > > > > ************************************************************************** > ****************************************************** > The information in this email is confidential and may be legally > privileged. If you have received this email in error or are > not the intended recipient, please immediately notify the sender and > delete this message from your computer. Any use, distribution, > or copying of this email other than by the intended recipient is strictly > prohibited. All messages sent to and from us may be > monitored to ensure compliance with internal policies and to protect our > business. > Emails are not secure and cannot be guaranteed to be error free as they > can be intercepted, amended, lost or destroyed, > or contain viruses. Anyone who communicates with us by email is taken to > accept these risks. > > 收发邮件者请注意： > 本邮件含保密信息，若误收本邮件，请务必通知发送人并直接删去，不得使用、传播或复制本邮件。 > 进出邮件均受到本公司合规监控。邮件可能发生被截留、被修改、丢失、被破坏或包含计算机病毒等不安全情况。 > ************************************************************************** > ******************************************************
