With regard to:-<br><br>2) You use the capabilities of the Drools GUI tools (such as Guvnor), which<br>
allows entering rules, objects and actions via GUI tools.<br>
Here, I don't get the point whether a part of the java code is generated<br>
automatically, or whether you have to write your java classes by yourself, as<br>
presented in possibility 1 (above), but without coding the rules by yourself in<br>
the source code / external input files.<br><br>You can choose whether you want to upload a POJO Java model or declare one within Guvnor itself (this feature is also available in DRL too - see "declare" in the "Expert" documentation). Guvnor basically offers a graphical means to (in reality) a sub-set of "drools" feature-set ("drools" as in Drools Expert, Drools Fusion, Drols Flow - now jBPM5 - and Drools Solver). Guvnor does offer some things of it's own (in addition to graphical editing: testing services, centralised repository etc). However you choose to use "drools" a domain Java model will be needed (POJOs, declarative DRL, defined in Guvnor etc) and rules (DRL, DSL, decision tables etc) authored (text files, Guvnor's guided editors etc): How and where is largely up to you.<br>
<br>With kind regards,<br><br>Mike <br><br><div class="gmail_quote">2011/2/3 Mauricio Salatino <span dir="ltr"><<a href="mailto:salaboy@gmail.com">salaboy@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I'm just wanna add some comments <br><br><div class="gmail_quote">2011/2/3 Esteban Aliverti <span dir="ltr"><<a href="mailto:esteban.aliverti@gmail.com" target="_blank">esteban.aliverti@gmail.com</a>></span><div class="im">
<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<div><div><br></div><div><font color="#000066">1) You write a java program, rules / actions are hard coded inline or saved<br>in text files / excel sheets / XML files etc. After importing the necessary<br>
drools classes you call the drools interface routines, with the following<br>functionalities:<br>load rules, providing working memory, adding facts und finally starting the rule<br>engine (e.g. firing rules).</font></div>
<div><br></div></div><div>Just some corrections here. The steps would be: load rules, get a working memory (kbase), create a session from the working memory, insert facts to it (this will start the pattern matching algorithm), fire the action part of the rules that matches the inserted Facts.</div>
</blockquote></div><div>The working memory is the knowledge session (not the kbase) where all your facts will live. <br>The main advantage of this approach is to have the business rules / logic decoupled from your application and declarative expressed. <br>
Remember that the rule engine will not evaluate the rules in a sequential order (in contrast with IF and CASE statements) and the rule engine design was conceived thinking to handle huge amount of rules and the evaluation of these rules are optimized.<br>
<br><br></div><div><div></div><div class="h5"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>
<div><br><br><font color="#000066">2) You use the capabilities of the Drools GUI tools (such as Guvnor), which<br>allows entering rules, objects and actions via GUI tools.<br>Here, I don't get the point whether a part of the java code is generated<br>
automatically, or whether you have to write your java classes by yourself, as<br>presented in possibility 1 (above), but without coding the rules by yourself in<br>the source code / external input files.</font></div><div>
<font color="#000066"><br></font></div></div><div>Guvnor is just used as a centralized place to create (if you want to), maintain and distribute your rules. You have different editor for different representations, like DRL, BRL (using a Guided Editor), Decision Table, DSL, etc. Guvnor then exposes these assets (their source code or binary representation) through different URLs. So, your application should read the rules (in the first step of the previous section) from Guvnor using HTTP (or even webdav) to create the working memory.</div>
<div><br></div><div>Hope this helps to clarify a little bit your thoughts.</div><div><br></div><div>Best Regards,</div><div> </div><div><br>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX<br><font color="#888888">
<br>Esteban Aliverti<br>- Developer @ <a href="http://www.plugtree.com" target="_blank">http://www.plugtree.com </a><br>- Blog @ <a href="http://ilesteban.wordpress.com" target="_blank">http://ilesteban.wordpress.com</a></font><div>
<div></div><div><br>
<br><br><div class="gmail_quote">On Thu, Feb 3, 2011 at 2:26 PM, Martin Richardsen <span dir="ltr"><<a href="mailto:jaichwill@gmail.com" target="_blank">jaichwill@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
I am a complete novice concerning Drools and have some basic questions,<br>
which arised after studying the drools documentation and some examples as well.<br>
<br>
As far as I got it right, you have two possibilities to work with drools<br>
<br>
1) You write a java program, rules / actions are hard coded inline or saved<br>
in text files / excel sheets / XML files etc. After importing the necessary<br>
drools classes you call the drools interface routines, with the following<br>
functionalities:<br>
load rules, providing working memory, adding facts und finally starting the rule<br>
engine (e.g. firing rules).<br>
<br>
2) You use the capabilities of the Drools GUI tools (such as Guvnor), which<br>
allows entering rules, objects and actions via GUI tools.<br>
Here, I don't get the point whether a part of the java code is generated<br>
automatically, or whether you have to write your java classes by yourself, as<br>
presented in possibility 1 (above), but without coding the rules by yourself in<br>
the source code / external input files.<br>
<br>
I would be very pleased, if anyone could explain me the essential difference<br>
between the two approaches and accordingly tell me what the advantage of using<br>
method 2) would be in contrast to method 1), particularly concerning the<br>
necessary java coding.<br>
<br>
<br>
---<br>
<br>
<br>
Well and there would be another question, if you write down your rules and the<br>
corresponding software, which accesses the rules, is it possible to add some<br>
rules later, without rewriting/recompiling your software?<br>
<br>
<br>
Thanks in advance!<br>
<br>
Cheers, Martin.<br>
<br>
_______________________________________________<br>
rules-users mailing list<br>
<a href="mailto:rules-users@lists.jboss.org" target="_blank">rules-users@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
</blockquote></div><br></div></div></div>
<br>_______________________________________________<br>
rules-users mailing list<br>
<a href="mailto:rules-users@lists.jboss.org" target="_blank">rules-users@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
<br></blockquote></div></div></div><font color="#888888"><br><br clear="all"><br>-- <br> - CTO @ <a href="http://www.plugtree.com" target="_blank">http://www.plugtree.com</a> <br> - MyJourney @ <a href="http://salaboy.wordpress.com" target="_blank">http://salaboy.wordpress.com</a><br>
- Co-Founder @ <a href="http://www.jbug.com.ar" target="_blank">http://www.jbug.com.ar</a><br> <br> - Salatino "Salaboy" Mauricio -<br>
</font><br>_______________________________________________<br>
rules-users mailing list<br>
<a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
<br></blockquote></div><br>