4:59 p.m.
Author: objectiser
Date: 2008-11-14 10:59:58 -0500 (Fri, 14 Nov 2008)
New Revision: 444
Added:
cdl/trunk/docs/docbook/gettingstartedguide/src/main/images/TrailBlazerMonitorError.jpg
Modified:
cdl/trunk/docs/docbook/gettingstartedguide/src/main/module/soagwithcdl.xml
cdl/trunk/docs/docbook/samplesguide/src/main/module/cdlvalidator.xml
Log:
Updated to include instructions on deploying trailblazer client that results in unexpected
message error.
Added:
cdl/trunk/docs/docbook/gettingstartedguide/src/main/images/TrailBlazerMonitorError.jpg
===================================================================
(Binary files differ)
Property changes on:
cdl/trunk/docs/docbook/gettingstartedguide/src/main/images/TrailBlazerMonitorError.jpg
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Modified: cdl/trunk/docs/docbook/gettingstartedguide/src/main/module/soagwithcdl.xml
===================================================================
--- cdl/trunk/docs/docbook/gettingstartedguide/src/main/module/soagwithcdl.xml 2008-11-13
13:28:01 UTC (rev 443)
+++ cdl/trunk/docs/docbook/gettingstartedguide/src/main/module/soagwithcdl.xml 2008-11-14
15:59:58 UTC (rev 444)
@@ -325,7 +325,7 @@
<orderedlist>
<listitem>
-From the <filename>trailblazer</filename> folder, execute the command to
start the ESB: <emphasis role="bold">ant deploy</emphasis>
+From the <filename>trailblazer</filename> folder, execute the following
command to deploy the example to the ESB: <emphasis role="bold">ant
deploy</emphasis>
<para>
this should deploy the ESB and WAR files to your JBoss AS
<filename>server/default</filename>.
</para>
@@ -386,6 +386,37 @@
</section>
+ <section>
+ <title>Detecting a Validation Error</title>
+
+ <para>
+To demonstrate the detection of validation errors, there is an alternative implementation
of the trailblazer modules that behaviour differently to the choreography that is being
monitored. Specifically, the credit score threshold used to determine whether a loan
request should be issued to the banks, is raised from 4 to 7.
+ </para>
+
+ <para>
+To deploy the version of the TrailBlazer example that results in validation errors,
then:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+From the <filename>$Overlord/samples/trailblazer</filename> folder, execute
the following command to deploy the example to the ESB: <emphasis
role="bold">ant deploy-error-client</emphasis>.
+ </listitem>
+ </itemizedlist>
+
+ <para>
+The next step is to issue more transactions, until a credit check score occurs that is
between 4 and 6 inclusive. This will result in a
<emphasis>insufficientCredit</emphasis> interaction being reported, which
would be unexpected in terms of the choreography.
+ </para>
+
+ <imageobject>
+ <imagedata fileref="images/TrailBlazerMonitorError.jpg"
align="center" width="4in" />
+ </imageobject>
+
+ <para>
+When errors, such as unexpected messages, are detected by the service validators and
reported to the Choreography Monitor, they are displayed in red.
+ </para>
+
+ </section>
+
</section>
</chapter>
Modified: cdl/trunk/docs/docbook/samplesguide/src/main/module/cdlvalidator.xml
===================================================================
--- cdl/trunk/docs/docbook/samplesguide/src/main/module/cdlvalidator.xml 2008-11-13
13:28:01 UTC (rev 443)
+++ cdl/trunk/docs/docbook/samplesguide/src/main/module/cdlvalidator.xml 2008-11-14
15:59:58 UTC (rev 444)
@@ -115,6 +115,13 @@
</listitem>
</orderedlist>
+ <para>
+ </para>
+
+ <para>
+The above steps show how changing the service implementation without updating a
choreography can result in behavioural validation errors being detected. The other way to
demonstrate the effect of this change is to simply run the ant task: <emphasis
role="bold">ant deploy-error-client</emphasis>, from the
<filename>$Overlord/samples/trailblazer</filename> folder, which achieves the
same results.
+ </para>
+
</section>
</chapter>