[jboss-svn-commits] JBL Code SVN: r34175 - in labs/jbossrules/trunk/drools-docs: drools-docs-expert/src/main/docbook/en-US/Chapter-Examples and 3 other directories.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Mon Jul 26 07:30:50 EDT 2010
Author: ge0ffrey
Date: 2010-07-26 07:30:49 -0400 (Mon, 26 Jul 2010)
New Revision: 34175
Modified:
labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Authoring/Section-Decision_Tables.xml
labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Examples/Section-SodukiExample.xml
labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-IDE/Chapter-QuickStart.xml
labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Rule_Engine/Section-The_Drools_Rule_Engine.xml
labs/jbossrules/trunk/drools-docs/drools-docs-flow/src/main/docbook/en-US/Chapter-HumanTasks/Chapter-HumanTasks.xml
Log:
typo's, style and don't wrap a pure <programlisting> in <para>
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Authoring/Section-Decision_Tables.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Authoring/Section-Decision_Tables.xml 2010-07-26 11:20:44 UTC (rev 34174)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Authoring/Section-Decision_Tables.xml 2010-07-26 11:30:49 UTC (rev 34175)
@@ -738,10 +738,10 @@
<para>The code to run this is simple:</para>
- <programlisting role="JAVA">//first we compile the spreadsheet with the template
-//to create a whole lot of rules.
+ <programlisting role="JAVA">// First we compile the spreadsheet with the template
+// to create a whole lot of rules.
final ExternalSpreadsheetCompiler converter = new ExternalSpreadsheetCompiler();
-//the data we are interested in starts at row 2, column 2 (e.g. B2)
+// The data we are interested in starts at row 2, column 2 (e.g. B2)
final String drl = converter.compile(getSpreadsheetStream(), getRulesStream(), 2, 2);
</programlisting>
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Examples/Section-SodukiExample.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Examples/Section-SodukiExample.xml 2010-07-26 11:20:44 UTC (rev 34174)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Examples/Section-SodukiExample.xml 2010-07-26 11:30:49 UTC (rev 34175)
@@ -36,7 +36,7 @@
you insert a new number it should be unique in its particular
3x3 zone, row and column.</para>
- <para>See <programlisting>URL: http://en.wikipedia.org/wiki/Sudoku</programlisting>
+ <para>See <link xlink:href="http://en.wikipedia.org/wiki/Sudoku">Wikipedia</link>
for a more detailed description.</para>
</section>
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-IDE/Chapter-QuickStart.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-IDE/Chapter-QuickStart.xml 2010-07-26 11:20:44 UTC (rev 34174)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-IDE/Chapter-QuickStart.xml 2010-07-26 11:30:49 UTC (rev 34175)
@@ -305,7 +305,7 @@
you can then deploy it as a binary file. Alternatively, you can use the
following snippet of code to convert the brl to a drl rule.</para>
- <programlisting role="JAVA">BRXMLPersitence read = BRXMLPersitence.getInstance();
+ <programlisting role="JAVA">BRXMLPersistence read = BRXMLPersistence.getInstance();
BRDRLPersistence write = BRDRLPersistence.getInstance();
String brl = ... // read from the .brl file as needed...
String outputDRL = write.marshall(read.unmarshal(brl));
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Rule_Engine/Section-The_Drools_Rule_Engine.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Rule_Engine/Section-The_Drools_Rule_Engine.xml 2010-07-26 11:20:44 UTC (rev 34174)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-expert/src/main/docbook/en-US/Chapter-Rule_Engine/Section-The_Drools_Rule_Engine.xml 2010-07-26 11:30:49 UTC (rev 34175)
@@ -399,7 +399,7 @@
<programlisting role="JAVA">Cheese stilton = new Cheese("stilton");
FactHandle stiltonHandle = session.insert( stilton );
-....
+...
session.retract( stiltonHandle ); </programlisting>
</section>
@@ -421,7 +421,7 @@
<programlisting role="JAVA">Cheese stilton = new Cheese("stilton");
FactHandle stiltonHandle = workingMemory.insert( stilton );
-....
+...
stilton.setPrice( 100 );
workingMemory.update( stiltonHandle, stilton ); </programlisting>
</section>
@@ -678,7 +678,7 @@
from the <code>RuleBase</code>, because without it you can get memory leaks.</para>
<example>
- <title>Createing a <code>StatefulSession</code></title>
+ <title>Creating a <code>StatefulSession</code></title>
<programlisting role="JAVA">StatefulSession session = ruleBase.newStatefulSession();</programlisting>
</example>
</section>
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-flow/src/main/docbook/en-US/Chapter-HumanTasks/Chapter-HumanTasks.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-flow/src/main/docbook/en-US/Chapter-HumanTasks/Chapter-HumanTasks.xml 2010-07-26 11:20:44 UTC (rev 34174)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-flow/src/main/docbook/en-US/Chapter-HumanTasks/Chapter-HumanTasks.xml 2010-07-26 11:30:49 UTC (rev 34175)
@@ -256,7 +256,7 @@
the implementation of the following methods for interacting with Human
Tasks:</para>
- <para><programlisting role="JAVA">
+ <programlisting role="JAVA">
public void start( long taskId, String userId, TaskOperationResponseHandler responseHandler )
public void stop( long taskId, String userId, TaskOperationResponseHandler responseHandler )
public void release( long taskId, String userId, TaskOperationResponseHandler responseHandler )
@@ -267,7 +267,7 @@
TaskOperationResponseHandler responseHandler )
public void complete( long taskId, String userId, ContentData outputData,
TaskOperationResponseHandler responseHandler )
-...</programlisting></para>
+...</programlisting>
<para>Using this methods we will implement any kind of GUI that the end
user will use to do the task that they have assigned. If you take a look
@@ -290,18 +290,18 @@
<listitem>
<para><emphasis role="bold">responseHandler</emphasis>: this is the
- handler have responsability to catch the response and get the
+ handler have responsibility to catch the response and get the
results or just let us know that the task is already
finished.</para>
</listitem>
</itemizedlist>
<para>As you can imagine all the methods create a message that will be
- sended to the server, and the server will execute the logic that
+ send to the server, and the server will execute the logic that
implement the correct action. A creation of one of this messages will be
like this:</para>
- <para><programlisting role="JAVA">
+ <programlisting role="JAVA">
public void complete(long taskId,
String userId,
ContentData outputData,
@@ -321,7 +321,7 @@
session.write( cmd );
}</programlisting>
- Here we can see that a Command is created and the arguments
+ <para>Here we can see that a Command is created and the arguments
of the method are inserted inside the command with the type of operation
that we are trying to execute and then this command is sended to the
server with session.write( cmd ) method.</para>
More information about the jboss-svn-commits
mailing list