<?xml version="1.0" encoding="ISO-8859-1"?>

<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
	<channel>
		<title>Java Programming Forum - Learn Java Programming - Blogs - Drools</title>
		<link>http://www.java-forums.org/blogs/drools/</link>
		<description>Java Programming Forum - Learning Java easily</description>
		<language>en</language>
		<lastBuildDate>Tue, 18 Jun 2013 04:55:00 GMT</lastBuildDate>
		<generator>vBulletin</generator>
		<ttl>60</ttl>
		<image>
			<url>http://www.java-forums.org/images/misc/rss.jpg</url>
			<title>Java Programming Forum - Learn Java Programming - Blogs - Drools</title>
			<link>http://www.java-forums.org/blogs/drools/</link>
		</image>
		<item>
			<title>Drools Components</title>
			<link>http://www.java-forums.org/blogs/drools/998-drools-components.html</link>
			<pubDate>Sun, 04 Mar 2012 08:57:14 GMT</pubDate>
			<description>1. *Rules* – Where conditions are specified (If a then b) 
2. *Facts* – Simple objects (POJOs). E.g, a Bank Account fact consists of an account...</description>
			<content:encoded><![CDATA[<blockquote class="blogcontent restore">1. <b>Rules</b> – Where conditions are specified (If a then b)<br />
2. <b>Facts</b> – Simple objects (POJOs). E.g, a Bank Account fact consists of an account number, someone’s id and balance.<br />
3.<b> Knowledge Base</b> –is where rules are built and loaded into a structure that gets implemented  by the Rete algorithm.<br />
4. <b>Session</b> – Here facts are placed. Facts are inserted into a session. A session can be State less or State full. Facts in the statefull shall be present in a constant rule alignment once they are inserted.<br />
5. <b>Activation</b> – It might be a rule’s “then” part. When you find a rule to be true then place Agenda into activation. It shall be noticed that all the activations are only placed in Agenda.<br />
6. <b>Agenda</b> –Activations wait to get fired in agenda. For state full sessions, all rules are being fired. Once a fact is inserted all of the activations are placed in agenda, already. When fire rules of session are called explicitly the execution of activations take place. When activation gets executed once facts might be update or retracted that may place new activations in agenda. New activations will be fired by the Drools engine until the agenda gets empty.<br />
<br />
<div style="text-align: center;"><img src="http://www.java-forums.org/attachments/jdbc/3152d1330851417-problems-preparestatement-1.jpg" border="0" alt="Name:  1.JPG
Views: 108
Size:  18.5 KB" class="thumbnail" style="float:CONFIG" /></div><b><div style="text-align: center;">Drools Components</div></b></blockquote>

]]></content:encoded>
			<dc:creator>Drools</dc:creator>
			<guid isPermaLink="true">http://www.java-forums.org/blogs/drools/998-drools-components.html</guid>
		</item>
		<item>
			<title>How is JBoss Drools is made up</title>
			<link>http://www.java-forums.org/blogs/drools/997-how-jboss-drools-made-up.html</link>
			<pubDate>Sun, 04 Mar 2012 08:54:37 GMT</pubDate>
			<description><![CDATA[There are 2 main parts of Drools: 
 
*Authoring & Runtime* 
 
Creation Rules files (.DRL) are involved in authoring process. They consists of rules...]]></description>
			<content:encoded><![CDATA[<blockquote class="blogcontent restore">There are 2 main parts of Drools:<br />
<br />
<b>Authoring &amp; Runtime</b><br />
<br />
Creation Rules files (.DRL) are involved in authoring process. They consists of rules that are being fed to a parser. Correct syntax of rules is checked by parser which creates intermediate structure so that to describe certain rules. Then it is passed on to Package Builder that creates the packages. After this, any code generation as well as compilation is undertaken that is essential to create package.<br />
<br />
RuleBase, being a runtime component is built from 1 or more then 1 packages. At any time, more than one working memories could be instantiated by the RuleBase. Numbers of sub components are present in working memory which includes Truth Maintenance system, Working Memory Event Support &amp; Agenda and Agenda Event Support.</blockquote>

]]></content:encoded>
			<dc:creator>Drools</dc:creator>
			<guid isPermaLink="true">http://www.java-forums.org/blogs/drools/997-how-jboss-drools-made-up.html</guid>
		</item>
		<item>
			<title>Why using a Rule Engine ?</title>
			<link>http://www.java-forums.org/blogs/drools/996-why-using-rule-engine.html</link>
			<pubDate>Sun, 04 Mar 2012 08:53:11 GMT</pubDate>
			<description>Rule systems are able to solve hard problems by providing the detail of the arrival of the solution and also why every decision was been taken along...</description>
			<content:encoded><![CDATA[<blockquote class="blogcontent restore">Rule systems are able to solve hard problems by providing the detail of the arrival of the solution and also why every decision was been taken along the way.<br />
<br />
Major benefits of Rule Engine are:<br />
<br />
<b>Logic &amp; Data Separation</b><br />
To break down the domain objects from business rules could make it possible to easily maintain the application. This is possible because it may shield from the future alterations.<br />
<br />
<b>Speed &amp; Scalability</b><br />
Several times, “if” condition is applied this is not actually needed. The Rete algorithm makes the replacement of all “ifs”…(as implemented by Drools) and then statements along with a network that is optimized.<br />
<br />
<b>Knowledge Centralization</b><br />
Repository of knowledge is created by using the rules. For business policy, it could be the single point of truth. Rules are ideally so readable that they might serve the purpose of documentations.<br />
<br />
<b>Tool’s Integration</b><br />
To write the rules actually means to be accustomed to the Rule debugging, validation and language. Eclipse is found to give an excellent delivery tool which tests your rules.</blockquote>

]]></content:encoded>
			<dc:creator>Drools</dc:creator>
			<guid isPermaLink="true">http://www.java-forums.org/blogs/drools/996-why-using-rule-engine.html</guid>
		</item>
		<item>
			<title>Drools Components and Terminology</title>
			<link>http://www.java-forums.org/blogs/drools/995-drools-components-terminology.html</link>
			<pubDate>Sun, 04 Mar 2012 08:51:30 GMT</pubDate>
			<description>Objects used by the Drools are market out by the rules and patterns which are responsible for invoking the certain actions: 
 
 
* Drool objects are...</description>
			<content:encoded><![CDATA[<blockquote class="blogcontent restore">Objects used by the Drools are market out by the rules and patterns which are responsible for invoking the certain actions:<br />
<br />
<ul><li style="">Drool objects are considered as the Java objects. They are usually presented by the XML schemas or instances of the Java classes.</li><li style="">A patter being a coded expression is involved in the manipulation of 1 or more than 1 objects so that to create a pattern for making, adapting behavior, according to the designed logic.</li><li style="">Working Memory drools stores its objects in working memory.</li><li style="">Actions are basically those operations which might alter the working memory.</li><li style="">A rule can perform different actions, like:</li></ul><br />
<div style="margin-left:40px">– Add/remove object, from the working memory<br />
– Modification of an object might take place.<br />
– Execute one method at one of the objects</div></blockquote>

]]></content:encoded>
			<dc:creator>Drools</dc:creator>
			<guid isPermaLink="true">http://www.java-forums.org/blogs/drools/995-drools-components-terminology.html</guid>
		</item>
		<item>
			<title>Advantages of the Drools rule engine</title>
			<link>http://www.java-forums.org/blogs/drools/994-advantages-drools-rule-engine.html</link>
			<pubDate>Sun, 04 Mar 2012 08:48:15 GMT</pubDate>
			<description>Drools rule engine offers these advantages. 
 
* It separates conditions and applications 
 
 
 
* They are present in separated files 
* Different...</description>
			<content:encoded><![CDATA[<blockquote class="blogcontent restore">Drools rule engine offers these advantages.<br />
<ul><li style="">It separates conditions and applications</li></ul><br />
<div style="margin-left:40px"><ul><li style="">They are present in separated files</li><li style="">Different people groups can modify them</li><li style="">After changing a rule, recompilation is not needed. Redeployment is also not needed in the whole application.</li><li style="">To control an application’s flow, put rules at one place</li></ul></div><ul><li style="">All the complexed statements can be replaced by rules in an easier or understandable way</li></ul><br />
<div style="margin-left:40px"><ul><li style="">Rule language is not tough to be learnt.</li><li style="">An “Eclipse plug in” makes it an easy task to write down the rules and also makes it possible to look at the RETE tree.</li></ul></div><ul><li style="">Complicated problems are solved by using rules that doesn’t solve the complex algorithms. Rules are easily understandable in comparison to code.</li></ul><br />
<div style="margin-left:40px"><ul><li style="">Focus is at what, not how, in case of declarative programming.</li></ul></div><ul><li style="">Rules easily solve group of problems </li></ul></blockquote>

]]></content:encoded>
			<dc:creator>Drools</dc:creator>
			<guid isPermaLink="true">http://www.java-forums.org/blogs/drools/994-advantages-drools-rule-engine.html</guid>
		</item>
		<item>
			<title>Drools Overview</title>
			<link>http://www.java-forums.org/blogs/drools/993-drools-overview.html</link>
			<pubDate>Sun, 04 Mar 2012 08:46:05 GMT</pubDate>
			<description>Drools, BRMS i.e. business rule management system consists of a forward chaining inference based rule engine. Correctly, it is called production rule...</description>
			<content:encoded><![CDATA[<blockquote class="blogcontent restore">Drools, BRMS i.e. business rule management system consists of a forward chaining inference based rule engine. Correctly, it is called production rule system which uses enhanced Rete algorithm implementation.<br />
For its business rule engine as well as its enterprise framework, Drools provides support to JSR-94 standard. This is done for maintenance, construction &amp; enforcement of organization’s business policies, services or applications.<br />
<br />
Pluggable language implementations are being allowed by the Drools. Now rules are written in Groovy, MVEL, Java and python. Declarative programming is provided by the drools and it is quite flexible to match the problem domain’s semantics with the DSL i.e. domain specific languages through XML, by using a schema that has been define particularly for sake of problem domain. Domain specific languages possess XML elements as well attributes that present the problem domain.</blockquote>

]]></content:encoded>
			<dc:creator>Drools</dc:creator>
			<guid isPermaLink="true">http://www.java-forums.org/blogs/drools/993-drools-overview.html</guid>
		</item>
	</channel>
</rss>
