[savara-commits] savara SVN: r432 - in trunk: docs/gettingstartedguide/src/main/en-US/module and 1 other directories.
do-not-reply at jboss.org
do-not-reply at jboss.org
Thu Oct 7 07:23:55 EDT 2010
Author: objectiser
Date: 2010-10-07 07:23:55 -0400 (Thu, 07 Oct 2010)
New Revision: 432
Added:
trunk/docs/gettingstartedguide/src/main/en-US/images/SAVARAMonitorPurchasing1.png
trunk/docs/gettingstartedguide/src/main/en-US/images/SAVARAMonitorPurchasing2.png
Modified:
trunk/docs/gettingstartedguide/src/main/en-US/module/runtimevalidation.xml
trunk/tools/pom.xml
Log:
Change purchasing example docs and update link to pi4soa update site for build.
Added: trunk/docs/gettingstartedguide/src/main/en-US/images/SAVARAMonitorPurchasing1.png
===================================================================
(Binary files differ)
Property changes on: trunk/docs/gettingstartedguide/src/main/en-US/images/SAVARAMonitorPurchasing1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/docs/gettingstartedguide/src/main/en-US/images/SAVARAMonitorPurchasing2.png
===================================================================
(Binary files differ)
Property changes on: trunk/docs/gettingstartedguide/src/main/en-US/images/SAVARAMonitorPurchasing2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Modified: trunk/docs/gettingstartedguide/src/main/en-US/module/runtimevalidation.xml
===================================================================
--- trunk/docs/gettingstartedguide/src/main/en-US/module/runtimevalidation.xml 2010-10-01 14:34:26 UTC (rev 431)
+++ trunk/docs/gettingstartedguide/src/main/en-US/module/runtimevalidation.xml 2010-10-07 11:23:55 UTC (rev 432)
@@ -146,31 +146,46 @@
<section>
<title>Web Service / WS-BPEL Example - Purchasing</title>
- <note>
<para>
- Savara now includes the ability to validate web services (and therefore BPEL
+ Savara includes the ability to validate web services (and therefore BPEL
processes) that use the jbossws-native stack. However the ODE engine, used
to execute BPEL processes within RiftSaw, currently optimises communications
between BPEL processes executing within the same engine, so that the communications
do not occur using the Web Service stack. This means that Savara is currently
- unable to validate these interactions. Therefore it is currently recommended to
- implement the 'Credit Agency' participant as a JAX-WS service. More information
- on this will be available on the Savara blog.
+ unable to validate these interactions by default.
</para>
- </note>
+ <para>
+ There are two solutions to this problem. The first is to disable the interprocess
+ communications used between the two BPEL processes, which will be the approach
+ described in this section. The other approach is to implement the 'Credit Agency'
+ participant as a JAX-WS service.
+ </para>
+
<section>
<title>Deploying the Example</title>
<para>
- The first step is to deploy the BPEL processes for the Store and CreditAgency
+ Once the BPEL processes have been generated, and the implementation details
+ added, it is currently necessary to disable the 'inter-process' communication
+ that is used to communicate between the two processes (an ODE optimization
+ when the processes are running in the same engine). This is achieved by
+ editing the deployment descriptor for the Store process (using a text editor
+ rather than the Eclipse form editor), and add the attribute
+ <emphasis>usePeer2Peer="false"</emphasis> to the <emphasis>invoke</emphasis> element.
+ </para>
+
+ <para>
+ The next step is to deploy the BPEL processes for the Store and CreditAgency
participants to a JBossAS server running RiftSaw. This can be achieved
using the Eclipse Web Tooling Project (WTP) server support, in conjunction with
the JBoss Tools features mentioned in the installation section.
</para>
<para>
- Create a JBossAS server, configured to point to a JBossAS environment that has
+ Create a JBossAS server entry in the <emphasis>Servers</emphasis> view, using
+ the <emphasis>New->Server</emphasis> menu item on the view's context menu.
+ Configure the server entry to point to a JBossAS environment that has
previously been configured to run RiftSaw. Select the server in the
<emphasis>Servers</emphasis> view, and then select the <emphasis>Add and Remove ...</emphasis>
menu item. This will show a dialog window that will include the CreditAgency
@@ -185,7 +200,9 @@
<para>
Start the server using the <emphasis>Start</emphasis> menu item associated with
- the JBossAS server in the <emphasis>Servers</emphasis> view. Once the server
+ the JBossAS server in the <emphasis>Servers</emphasis> view, or manually from
+ a terminal window in the JBossAS server's <filename>bin</filename> folder using
+ the <emphasis>run</emphasis> script. Once the server
has fully started, the BPEL processes should have been deployed.
</para>
@@ -197,8 +214,9 @@
<para>
The final step is to send a test message to the <emphasis>Store</emphasis>
BPEL process. This can be achieved by selecting the <filename>PurchaseGoodsProcess_Store.wsdl</filename>
- file, within the <emphasis>PurchaseGoodsProcess_Store</emphasis> project (bpelContents
- folder), and then select the menu item <emphasis>Web Services->Test with Web Services Explorer</emphasis>.
+ file, within the <emphasis>PurchaseGoodsProcess_Store</emphasis> project
+ (<filename>bpelContents</filename> folder), and then select the menu
+ item <emphasis>Web Services->Test with Web Services Explorer</emphasis>.
</para>
<para>
@@ -217,6 +235,39 @@
Then press the 'Ok' button further down the panel. This will send the message to the
Store process, and eventually cause a response to appear in the lower panel.
</para>
+
+ <para>
+ Four entries should appear in the SAVARA monitor, the buy request, credit check
+ request, credit check ok (response) and buy confirmed (response).
+ </para>
+
+ <imageobject>
+ <imagedata fileref="en-US/images/SAVARAMonitorPurchasing1.png" align="center" width="6in" />
+ </imageobject>
+
+ <para>
+ To demonstrate how an error would be detected and reported, issue a new request
+ such as:
+ </para>
+
+ <informalexample>
+ <programlisting role="XML" ><![CDATA[
+ <q0:BuyRequest id="2" amount="300" />
+ ]]></programlisting>
+ </informalexample>
+
+ <para>
+ This will result in an unexpected message to be reported, as there is a difference
+ between the choreography and the CreditAgency BPEL process (implementation).
+ The choreography defines that a valid credit check should be returned if the
+ amount is less than 250. However the BPEL process has implemented this condition
+ as a valid credit check is where the amount is less or equal to 500.
+ </para>
+
+ <imageobject>
+ <imagedata fileref="en-US/images/SAVARAMonitorPurchasing2.png" align="center" width="6in" />
+ </imageobject>
+
</section>
</section>
Modified: trunk/tools/pom.xml
===================================================================
--- trunk/tools/pom.xml 2010-10-01 14:34:26 UTC (rev 431)
+++ trunk/tools/pom.xml 2010-10-07 11:23:55 UTC (rev 432)
@@ -58,7 +58,8 @@
</repository>
<repository>
<id>pi4soa</id>
- <url>http://download.jboss.org/jbosstools/builds/nightly/3.2.helios/jbosstools-pi4soa/all/repo/</url>
+ <url>http://download.jboss.org/jbosstools/builds/staging/pi4soa/all/repo/</url>
+ <!-- >url>http://download.jboss.org/jbosstools/builds/nightly/3.2.helios/jbosstools-pi4soa/all/repo/</url -->
<layout>p2</layout>
<snapshots>
<enabled>true</enabled>
More information about the savara-commits
mailing list