12:31 a.m.
Author: objectiser
Date: 2010-06-24 18:31:56 -0400 (Thu, 24 Jun 2010)
New Revision: 789
Removed:
branches/RiftSaw-2.1.x/docs/docbook/gettingstartedguide/src/main/images/RetailerReqMesg.png
branches/RiftSaw-2.1.x/docs/docbook/gettingstartedguide/src/main/images/RetailerRespMesg.png
branches/RiftSaw-2.1.x/docs/docbook/gettingstartedguide/src/main/images/process-overview.png
branches/RiftSaw-2.1.x/samples/esb/webservice_esb_bpel/
Modified:
branches/RiftSaw-2.1.x/distribution/src/main/assembly/bin.xml
branches/RiftSaw-2.1.x/distribution/src/main/release/install/build.xml
branches/RiftSaw-2.1.x/docs/docbook/gettingstartedguide/src/main/module/examples.xml
branches/RiftSaw-2.1.x/docs/docbook/gettingstartedguide/src/main/module/installation.xml
Log:
Update to remove the webservice_esb_bpel example, and also remove the
'deploy-esb-examples' installation step.
Modified: branches/RiftSaw-2.1.x/distribution/src/main/assembly/bin.xml
===================================================================
--- branches/RiftSaw-2.1.x/distribution/src/main/assembly/bin.xml 2010-06-24 22:12:37 UTC
(rev 788)
+++ branches/RiftSaw-2.1.x/distribution/src/main/assembly/bin.xml 2010-06-24 22:31:56 UTC
(rev 789)
@@ -68,7 +68,6 @@
<include>esb/bpel_loan_fault/**</include>
<include>esb/invoke_esb_ebws/**</include>
<include>esb/simple_esb_proxy_invoke/**</include>
- <include>esb/webservice_esb_bpel/**</include>
<include>quickstart/bpel_event_listener/**</include>
<include>quickstart/hello_world/**</include>
<include>quickstart/hello_world_header_ode/**</include>
Modified: branches/RiftSaw-2.1.x/distribution/src/main/release/install/build.xml
===================================================================
--- branches/RiftSaw-2.1.x/distribution/src/main/release/install/build.xml 2010-06-24
22:12:37 UTC (rev 788)
+++ branches/RiftSaw-2.1.x/distribution/src/main/release/install/build.xml 2010-06-24
22:31:56 UTC (rev 789)
@@ -126,21 +126,7 @@
<delete file="${server.lib.dir}/gwt-console-rpc.jar"/>
</target>
- <target name="deploy-esb-examples" depends="check.deploy.props"
description="Deploys BPEL example to JBossESB">
- <echo message="Deploy BPEL ESB examples" />
- <copy todir="${esb.examples.dir}">
- <fileset dir="${samples}/${bpel-esb-examples}" />
- </copy>
- </target>
- <target name="undeploy-esb-examples"
depends="check.deploy.props" description="Undeploys BPEL example from
JBossESB">
- <echo message="Undeploy BPEL example" />
- <delete dir="${esb.examples.dir}/bpel_helloworld" />
- <delete dir="${esb.examples.dir}/bpel_loan_fault" />
- <delete dir="${esb.examples.dir}/webservice_esb_bpel" />
- </target>
-
-
<!-- install database specific driver -->
<target name="internal.install.riftsaw.into.jboss.db.hsql">
<!-- If the older version of h2 exists, as installed by the ESB (4.7), then
rename it -->
Deleted:
branches/RiftSaw-2.1.x/docs/docbook/gettingstartedguide/src/main/images/RetailerReqMesg.png
===================================================================
(Binary files differ)
Deleted:
branches/RiftSaw-2.1.x/docs/docbook/gettingstartedguide/src/main/images/RetailerRespMesg.png
===================================================================
(Binary files differ)
Deleted:
branches/RiftSaw-2.1.x/docs/docbook/gettingstartedguide/src/main/images/process-overview.png
===================================================================
(Binary files differ)
Modified:
branches/RiftSaw-2.1.x/docs/docbook/gettingstartedguide/src/main/module/examples.xml
===================================================================
---
branches/RiftSaw-2.1.x/docs/docbook/gettingstartedguide/src/main/module/examples.xml 2010-06-24
22:12:37 UTC (rev 788)
+++
branches/RiftSaw-2.1.x/docs/docbook/gettingstartedguide/src/main/module/examples.xml 2010-06-24
22:31:56 UTC (rev 789)
@@ -185,91 +185,6 @@
</para>
</section>
-
- <section>
- <title>ESB Examples - Order Management</title>
-
- <para>
- The ESB/BPEL example we are going to try out is the
- 'order management' example. When the ESB examples have been
- deployed, as described in the Installation chapter, then
- this example will be located in the
-
<filename>${JBossESB}/samples/quickstarts/webservice_esb_bpel</filename>
- folder.
- </para>
-
- <para>
- This example is different to the previous ESB example, in that
- it uses the BPEL process running inside RiftSaw as a Web Service.
- There is no direct invocation of the BPEL process.
- </para>
-
- <para>
- The first step is to deploy the example to the running JBossAS
- server. This is achieved using the following command:
- </para>
-
- <code>
- ant deploy
- </code>
-
- <para>
- When the ant script indicates that it has completed successfully,
- the next step is to invoke the BPEL process we have just deployed.
- This can be achieved using any SOAP client, such as SOAPUI (available
- from <ulink
url="http://www.soapui.org/">http://www.soapui.org/</ulink>).
- </para>
-
- <para>
- The WSDL definition is located in the <filename>bpel</filename>
- folder, and can be used to initialise the SOAPUI client. The
- service location is:
- <ulink
url="http://localhost:8080/Webservice_esb_bpel_Retailer">http://localhost:8080/Webservice_esb_bpel_Retailer</ulink>.
- </para>
-
- <para>
- An example message can be found in the
<filename>bpel/sampleData</filename>
- subfolder.
- </para>
-
- <imageobject>
- <imagedata fileref="images/RetailerReqMesg.png" align="center"
width="6in" />
- </imageobject>
-
- <para>
- When the message is submitted to the BPEL process, the response received is:
- </para>
-
- <imageobject>
- <imagedata fileref="images/RetailerRespMesg.png"
align="center" width="6in" />
- </imageobject>
-
- <para>
- This is an acknowledgement that the order has been received, and is awaiting
approval.
- At this point, you can access the BPEL console, to see that the BPEL process
triggered
- by the request message is still active.
- </para>
-
- <para>
- The next step is to access the order manager, located at:
- <ulink
url="http://localhost:8080/order-manager">http://localhost:8080/order-manager</ulink>.
- </para>
-
- <imageobject>
- <imagedata fileref="images/RetailerReqMesg.png" align="center"
width="6in" />
- </imageobject>
-
- <para>
- Once the order has been approved, by pressing the
<emphasis>Approve</emphasis> further processing
- will be triggered using ESB components, as outlined in the following diagram.
- </para>
-
- <imageobject>
- <imagedata fileref="images/process-overview.png"
align="center" width="6in" />
- </imageobject>
-
- </section>
-
<section>
<title>Importing Examples into Eclipse</title>
Modified:
branches/RiftSaw-2.1.x/docs/docbook/gettingstartedguide/src/main/module/installation.xml
===================================================================
---
branches/RiftSaw-2.1.x/docs/docbook/gettingstartedguide/src/main/module/installation.xml 2010-06-24
22:12:37 UTC (rev 788)
+++
branches/RiftSaw-2.1.x/docs/docbook/gettingstartedguide/src/main/module/installation.xml 2010-06-24
22:31:56 UTC (rev 789)
@@ -100,10 +100,6 @@
</para>
</note>
</listitem>
- <listitem>
- If JBossESB has been installed, then run: <command>ant
deploy-esb-examples</command> to
- install the BPEL/ESB examples into the JBossESB samples/quickstart folder.
- </listitem>
</itemizedlist>
</para>
</listitem>
@@ -122,10 +118,6 @@
RiftSaw from JBossAS. The database option should specify the same value used
during installation of RiftSaw.
</listitem>
- <listitem>
- If JBossESB has been installed, then run: <command>ant
undeploy-esb-examples</command> to
- remove the BPEL/ESB examples from the JBossESB samples/quickstart folder.
- </listitem>
</itemizedlist>
</para>
</listitem>