From overlord-commits at lists.jboss.org Fri Nov 14 10:59:58 2008
Content-Type: multipart/mixed; boundary="===============4417758303163794256=="
MIME-Version: 1.0
From: overlord-commits at lists.jboss.org
To: overlord-commits at lists.jboss.org
Subject: [overlord-commits] Overlord SVN: r444 - in cdl/trunk/docs/docbook:
 gettingstartedguide/src/main/module and 1 other directories.
Date: Fri, 14 Nov 2008 10:59:58 -0500
Message-ID: <E1L115S-0005c2-R0@committer01.frg.pub.inap.atl.jboss.com>

--===============4417758303163794256==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

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/TrailBlazerMo=
nitorError.jpg
Modified:
   cdl/trunk/docs/docbook/gettingstartedguide/src/main/module/soagwithcdl.x=
ml
   cdl/trunk/docs/docbook/samplesguide/src/main/module/cdlvalidator.xml
Log:
Updated to include instructions on deploying trailblazer client that result=
s in unexpected message error.

Added: cdl/trunk/docs/docbook/gettingstartedguide/src/main/images/TrailBlaz=
erMonitorError.jpg
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
(Binary files differ)


Property changes on: cdl/trunk/docs/docbook/gettingstartedguide/src/main/im=
ages/TrailBlazerMonitorError.jpg
___________________________________________________________________
Name: svn:mime-type
   + application/octet-stream

Modified: cdl/trunk/docs/docbook/gettingstartedguide/src/main/module/soagwi=
thcdl.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- 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 s=
tart the ESB: <emphasis role=3D"bold">ant deploy</emphasis>
+From the <filename>trailblazer</filename> folder, execute the following co=
mmand to deploy the example to the ESB: <emphasis role=3D"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 th=
e choreography that is being monitored. Specifically, the credit score thre=
shold used to determine whether a loan request should be issued to the bank=
s, is raised from 4 to 7.
+			</para>
+
+			<para>
+To deploy the version of the TrailBlazer example that results in validatio=
n errors, then:
+			</para>
+
+  			<itemizedlist>
+				<listitem>
+From the <filename>$Overlord/samples/trailblazer</filename> folder, execut=
e the following command to deploy the example to the ESB: <emphasis role=3D=
"bold">ant deploy-error-client</emphasis>.
+				</listitem>
+			</itemizedlist>
+
+			<para>
+The next step is to issue more transactions, until a credit check score oc=
curs that is between 4 and 6 inclusive. This will result in a <emphasis>ins=
ufficientCredit</emphasis> interaction being reported, which would be unexp=
ected in terms of the choreography.
+			</para>
+
+		<imageobject>
+			<imagedata fileref=3D"images/TrailBlazerMonitorError.jpg" align=3D"cent=
er" width=3D"4in" />
+		</imageobject>
+
+			<para>
+When errors, such as unexpected messages, are detected by the service vali=
dators 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
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- cdl/trunk/docs/docbook/samplesguide/src/main/module/cdlvalidator.xml	20=
08-11-13 13:28:01 UTC (rev 443)
+++ cdl/trunk/docs/docbook/samplesguide/src/main/module/cdlvalidator.xml	20=
08-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 updat=
ing a choreography can result in behavioural validation errors being detect=
ed. The other way to demonstrate the effect of this change is to simply run=
 the ant task: <emphasis role=3D"bold">ant deploy-error-client</emphasis>, =
from the <filename>$Overlord/samples/trailblazer</filename> folder, which a=
chieves the same results.
+	</para>
+
   </section>
 	=

 </chapter>


--===============4417758303163794256==--