[jboss-svn-commits] JBL Code SVN: r23159 - in labs/jbossrules/trunk/drools-docs: drools-docs-expert/en/Chapter-IDE and 3 other directories.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Sun Sep 28 23:34:30 EDT 2008
Author: michael.neale at jboss.com
Date: 2008-09-28 23:34:30 -0400 (Sun, 28 Sep 2008)
New Revision: 23159
Modified:
labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Deployment/Section-Deployment.xml
labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-IDE/Chapter-QuickStart.xml
labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Engine/Section-Rete_Algorithm.xml
labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Engine/Section-Rules.xml
labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Engine/Section-The_Drools_Rule_Engine.xml
labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Engine/Section-What_is_a_Rule_Engine.xml
labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Engine/Section-Why_use_a_Rule_Engine.xml
labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Language/Section-DSL.xml
labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Language/Section-Rule.xml
labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Language/Section-XML.xml
labs/jbossrules/trunk/drools-docs/drools-docs-introduction/en/Chapter-Install/Section-Maven_build.xml
Log:
JBRULES-1589 typos patch from Florent Ramiere
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Deployment/Section-Deployment.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Deployment/Section-Deployment.xml 2008-09-29 03:16:49 UTC (rev 23158)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Deployment/Section-Deployment.xml 2008-09-29 03:34:30 UTC (rev 23159)
@@ -203,7 +203,7 @@
<section>
<title>Out of process rule building</title>
- <para>In this case, rules are build into their binary process outside of
+ <para>In this case, rules are built into their binary process outside of
the runtime system (for example in a deployment server). The chief
advantage of deploying from an outside process is that the runtime
system can have minimal dependencies (just one jar). It also means that
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-IDE/Chapter-QuickStart.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-IDE/Chapter-QuickStart.xml 2008-09-29 03:16:49 UTC (rev 23158)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-IDE/Chapter-QuickStart.xml 2008-09-29 03:34:30 UTC (rev 23159)
@@ -497,7 +497,7 @@
<title>Domain Specific Languages</title>
<para>Domain Specific Languages (dsl) allow you to create a language that
- allows your rules to look like, rules ! Most often the domain specific
+ allows your rules to look like... rules ! Most often the domain specific
language reads like natural language. Typically you would look at how a
business analyst would describe the rule, in their own words, and then map
this to your object model via rule constructs. A side benefit of this is
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Engine/Section-Rete_Algorithm.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Engine/Section-Rete_Algorithm.xml 2008-09-29 03:16:49 UTC (rev 23158)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Engine/Section-Rete_Algorithm.xml 2008-09-29 03:34:30 UTC (rev 23159)
@@ -86,7 +86,7 @@
checks.</para>
<para>There are two two-input nodes; JoinNode and NotNode - both are
- types of BetaNodes. BetaNodes are use to compare 2 objects, and their
+ types of BetaNodes. BetaNodes are used to compare 2 objects, and their
fields, to each other. The objects may be the same or different types. By
convention we refer to the two inputs as left and right. The left input for
a BetaNode is generally a list of objects; in Drools this is a Tuple. The
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Engine/Section-Rules.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Engine/Section-Rules.xml 2008-09-29 03:16:49 UTC (rev 23158)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Engine/Section-Rules.xml 2008-09-29 03:34:30 UTC (rev 23159)
@@ -247,7 +247,7 @@
<para>So in Java we can say that a simple proposition is of the form
'variable' 'operator' 'value' - where we often refer to 'value' as being a
literal value - a proposition can be thought as a field constraint.
- Further to this propositions can be combined with conjunctive and
+ Further to this proposition can be combined with conjunctive and
disjunctive connectives, which is the logic theorists way of saying
'&&' and '||'. The following shows two open propositional
statements connected together with a single disjunctive connective.</para>
@@ -313,7 +313,7 @@
private String name;
private String studentName;
private int score;
-
+ ...
}
</programlisting>
@@ -325,7 +325,7 @@
List failedStudents = new ArrayList();
- for ( Iterator studentIter = students.iterator(); studentIter.hasNext() {
+ for ( Iterator studentIter = students.iterator(); studentIter.hasNext();) {
Student student = ( Student ) studentIter.next();
for ( Iterator it = student.getModules.iterator(); it.hasNext(); ) {
Module module = ( Module ) it.next();
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Engine/Section-The_Drools_Rule_Engine.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Engine/Section-The_Drools_Rule_Engine.xml 2008-09-29 03:16:49 UTC (rev 23158)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Engine/Section-The_Drools_Rule_Engine.xml 2008-09-29 03:34:30 UTC (rev 23159)
@@ -361,9 +361,9 @@
thus causing new work to be needed.
-->
- <para>When an Object is insert it returns a FactHandle. This FactHandle
+ <para>When an Object is inserted it returns a FactHandle. This FactHandle
is the token used to represent your insert Object inside the
- WorkingMemory, it is also how you will interact with the Working Memory
+ WorkingMemory, it will be used when interacting with the Working Memory
when you wish to retract or modify an object.</para>
<programlisting>Cheese stilton = new Cheese("stilton");
@@ -405,7 +405,7 @@
<title>Update</title>
<para>The Rule Engine must be notified of modified Facts, so that it can
- be re-process. Modification internally is actually a retract and then an
+ be re-processed. Modification internally is actually a retract and then an
insert; so it clears the WorkingMemory and then starts again. Use the
modifyObject method to notify the Working Memory of changed objects, for
objects that are not able to notify the Working Memory themselves.
@@ -653,7 +653,7 @@
external source). For instance, if a new working memory is created, and
no facts are asserted, calling the fireAllRules will cause the Initial
Fact to propagate, possibly activating rules (otherwise, nothing would
- happen as there are no other facts to start with).</para>
+ happen as there is no other fact to start with).</para>
</section>
</section>
@@ -949,7 +949,7 @@
<para>If we logically insert an object when there is an equal STATED
object it will fail and return null. If we STATE an object that has an
- exist equal object that is JUSTIFIED we override the Fact - how this
+ existing equal object that is JUSTIFIED we override the Fact - how this
override works depends on the configuration setting
"WM_BEHAVIOR_PRESERVE". When the property is set to discard we use the
existing handle and replace the existing instance with the new Object -
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Engine/Section-What_is_a_Rule_Engine.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Engine/Section-What_is_a_Rule_Engine.xml 2008-09-29 03:16:49 UTC (rev 23158)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Engine/Section-What_is_a_Rule_Engine.xml 2008-09-29 03:34:30 UTC (rev 23159)
@@ -101,8 +101,7 @@
<primary>Rete</primary>
</indexterm> Rete algorithm, <indexterm>
<primary>Leaps</primary>
- </indexterm> Leaps use to be supported but was removed due to poor
- maintenance. The Drools <indexterm>
+ </indexterm> Leaps used to be provided but was retired as it became unmaintaned. The Drools <indexterm>
<primary>Rete</primary>
</indexterm> Rete implementation is called ReteOO, signifying that
Drools has an enhanced and optimized implementation of the Rete algorithm
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Engine/Section-Why_use_a_Rule_Engine.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Engine/Section-Why_use_a_Rule_Engine.xml 2008-09-29 03:16:49 UTC (rev 23158)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Engine/Section-Why_use_a_Rule_Engine.xml 2008-09-29 03:34:30 UTC (rev 23159)
@@ -163,7 +163,7 @@
</itemizedlist></para>
<para>If rules are a new technology for your project teams, the overhead
- in getting going must be factored in. Its not a trivial technology, but
+ in getting going must be factored in. It is not a trivial technology, but
this document tries to make it easier to understand.</para>
<para>Typically in a modern OO application you would use a rule engine to
@@ -243,7 +243,7 @@
in the past (where there are control tables that store meta-data that
changes your applications behavior) - these can work well when the
control can remain very limited. However, they can quickly grow out of
- control if extended to much (such that only the original creators can
+ control if extended too much (such that only the original creators can
change the applications behavior) or they cause the application to
stagnate as they are too inflexible.</para>
</section>
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Language/Section-DSL.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Language/Section-DSL.xml 2008-09-29 03:16:49 UTC (rev 23158)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Language/Section-DSL.xml 2008-09-29 03:34:30 UTC (rev 23159)
@@ -82,7 +82,7 @@
<para>It is important to note that the DSL expressions are processed one
line at a time. This means that in the above example, all the text after
- "There is " to the end of the line will be included as the value for
+ "This is " to the end of the line will be included as the value for
"{something}" when it is interpolated into the target string. This may not
be exactly what you want, as you may want to "chain" together different
DSL expressions to generate a target expression. The best way around this
@@ -107,7 +107,7 @@
<para>It is a good idea to try and avoid punctuation in your DSL
expressions where possible, other then quotes and the like - keep it
- simple it things will be easier. Using a DSL can make debugging slightly
+ simple and things will be easier. Using a DSL can make debugging slightly
harder when you are first building rules, but it can make the maintenance
easier (and of course the readability of the rules).</para>
@@ -291,7 +291,7 @@
in the Matrix, our means of getting stuff into computers is still the old
fashioned way.</para>
- <para>Rules engines require a object or data model to operate on - in many
+ <para>Rules engines require an object or a data model to operate on - in many
cases you may know this up front. In other cases the model will be
discovered with the rules. In any case, rules generally work better with
simpler flatter object models. In some cases, this may mean having a rule
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Language/Section-Rule.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Language/Section-Rule.xml 2008-09-29 03:16:49 UTC (rev 23158)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Language/Section-Rule.xml 2008-09-29 03:34:30 UTC (rev 23159)
@@ -19,13 +19,13 @@
normally part of a procedural execution flow, where at a specific point in
time it checks the condition. Where as "when" indicates it's not tied to a
specific evaluation sequence or point in time, at any time during the life
- time of the engine "when" this occurs, do that. Rule</para>
+ time of the engine "when" this occurs, do that Rule.</para>
<para>A rule must have a name, and be a unique name for the rule package. If
you define a rule twice in the same DRL it produce an error while loading.
If you add a DRL that has includes a rule name already in the package, it
will replace the previous rule. If a rule name is to have spaces, then it
- will need to be in double quotes (its best to always use double
+ will need to be in double quotes (it is best to always use double
quotes).</para>
<para>Attributes are optional, and are described below (they are best kept
@@ -104,8 +104,7 @@
<para>default value : false</para>
<para>type : Boolean</para>
-
- <para>when a ruleflow-group becomes active or an agenda-group receives the focus any rules that ahve lock-on-active set to try cannot place activations onto the agenda, the rules are matched and the resulting activations discarded. This is a stronger version of no-loop. It's ideally for calculation rules where you have a number of rules that will modify a fact and you don't want any rule re-matching and firing. In summary fire these currently active rules and only these rules, no matter how the data changes, do not allow any more activations for the rules with the attribute set to true. When the ruleflow-group is no longer active or agenda-group loses the focus those rules with lock-on-active set to true can once again add activations onto the agenda.</para>
+ <para>when a ruleflow-group becomes active or an agenda-group receives the focus any rules that have lock-on-active set to try cannot place activations onto the agenda, the rules are matched and the resulting activations discarded. This is a stronger version of no-loop. It's ideally for calculation rules where you have a number of rules that will modify a fact and you don't want any rule re-matching and firing. In summary fire these currently active rules and only these rules, no matter how the data changes, do not allow any more activations for the rules with the attribute set to true. When the ruleflow-group is no longer active or agenda-group loses the focus those rules with lock-on-active set to true can once again add activations onto the agenda.</para>
</listitem>
</varlistentry>
@@ -189,7 +188,7 @@
</varlistentry>
<varlistentry>
- <term>date-exptires</term>
+ <term>date-expires</term>
<listitem>
<para>default value : N/A</para>
@@ -1023,7 +1022,7 @@
Working Memory is not aware of any of the nested values, and do not
know when they change; they should be considered immutable while any
of their parent references are inserted into the Working Memory. If
- you wish to modify a nested value you should remove he parent objects
+ you wish to modify a nested value you should remove the parent objects
first and re-assert afterwards. If you only have a single parent at
the root of the graph, when in the MVEL dialect, you can use the
'modify' keyword and its block setters to write the nested accessor
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Language/Section-XML.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Language/Section-XML.xml 2008-09-29 03:16:49 UTC (rev 23158)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-expert/en/Chapter-Rule_Language/Section-XML.xml 2008-09-29 03:34:30 UTC (rev 23159)
@@ -293,7 +293,7 @@
<para>The Eval element allows the execution of a valid snippet of Java
code - as long as it evaluates to a boolean (do not end it with a
semi-colon, as it is just a fragment) - this can include calling a
- function. The Eval is less efficient then then columns, as the rule engine
+ function. The Eval is less efficient than the columns, as the rule engine
has to evaluate it each time, but it is a "catch all" feature for when you
can express what you need to do with Column constraints.</para>
</section>
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-introduction/en/Chapter-Install/Section-Maven_build.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-introduction/en/Chapter-Install/Section-Maven_build.xml 2008-09-29 03:16:49 UTC (rev 23158)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-introduction/en/Chapter-Install/Section-Maven_build.xml 2008-09-29 03:34:30 UTC (rev 23159)
@@ -6,7 +6,7 @@
<title>Building the Source</title>
<para>Now that we have the source the next step is to build and install
- the source. Since version 3.1 Drools uses <indexterm> Maven 2 </indexterm> to build the system. There are two profiles
+ the source. Since version 3.1 Drools uses <indexterm><primary>Maven 2</primary></indexterm> to build the system. There are two profiles
available which enable the associated modules "documentation" and
"Eclipse"; this enables quicker building of the core modules for
developers. The Eclipse profile will download Eclipse into the
More information about the jboss-svn-commits
mailing list