[jbossws-commits] JBossWS SVN: r2330 - branches/jbossws-1.0/docs/user-guide/project/en/modules/wsbpel.
Author: alex.guizar(a)jboss.com
Date: 2007-02-09 22:11:57 -0500 (Fri, 09 Feb 2007)
New Revision: 2330
Modified:
branches/jbossws-1.0/docs/user-guide/project/en/modules/wsbpel/wsbpel.xml
Log:
JBWS-867
Modified: branches/jbossws-1.0/docs/user-guide/project/en/modules/wsbpel/wsbpel.xml
===================================================================
--- branches/jbossws-1.0/docs/user-guide/project/en/modules/wsbpel/wsbpel.xml 2007-02-10
01:52:14 UTC (rev 2329)
+++ branches/jbossws-1.0/docs/user-guide/project/en/modules/wsbpel/wsbpel.xml 2007-02-10
03:11:57 UTC (rev 2330)
@@ -90,7 +90,7 @@
<listitem><para>The
<literal><partnerLinks></literal> section lists the parties
that
interact with the process in the course of greeting the world. The sole partner
link shown
- here corresponds to the agent sending the person name (the
<emphasis>caller</emphasis>).
+ here corresponds to the agent sending the person name: (the caller).
</para></listitem>
<listitem><para>The
<literal><variables></literal> section defines the data items
held
@@ -195,7 +195,7 @@
<para>Before the process can serve requests, its definition must be stored in
the jBPM database.
The unit test setup code shown below performs this operation. This code comes from
- class
<classname>org.jboss.test.ws.jaxrpc.samples.wsbpel.JbpmBpelTestSetup</classname>.
+ class
<literal>org.jboss.test.ws.jaxrpc.samples.wsbpel.JbpmBpelTestSetup</literal>.
The argument is a zip file containing your BPEL process and related WSDL
interfaces. The <literal>submitRequest</literal> method submits the zip
file to a web module
deployed as part of the jBPM BPEL service. The web module connects to the database
and
@@ -240,7 +240,7 @@
</para>
<para>The definition of a BPEL process only includes the port types of the
participants, as
- mentioned in <link linkend="wsbpel.definition"
endterm="wsbpel.definition.title" />. On the
+ mentioned in <link linkend="wsbpel.definition">Defining a business
process</link>. On the
other hand, a JSR-109 deployment requires the presence of binding and service
elements. JBoss
BPEL supplies a tool that generates SOAP 1.1 binding and service elements required
for
deploying the web service provided by the process.</para>
@@ -304,7 +304,7 @@
<para>A separate descriptor,
<literal>bpel-application.xml</literal>, specifies the name of
the process definition.</para>
- <programlisting><bpelApplication name="HelloWorld"
xmlns="http://jbpm.org/bpel" /></programlisting>
+ <programlisting><![CDATA[<bpelApplication name="HelloWorld"
xmlns="http://jbpm.org/bpel" />]]></programlisting>
<note><para>This name will be used to retrieve the process definition
from the jBPM database.
It must match the process name in your BPEL document.</para></note>
@@ -318,9 +318,9 @@
<para>No special configuration is needed on the client side. You consume a
service provided by
a WS-BPEL process the same way you consume any other service.</para>
- <para>You can reuse the Java mapping artifacts produced in <link
linkend="wsbpel.artifacts"
- endterm="wsbpel.artifacts.title" /> to develop a <link
linkend="jsr109-clients">JSR-109 client
- </link>.</para>
+ <para>You can reuse the Java mapping artifacts produced in <link
linkend="wsbpel.artifacts">
+ Generating the required artifacts</link> to develop a <link
linkend="jsr109-clients">JSR-109
+ client</link>.</para>
<programlisting><![CDATA[InitialContext iniCtx = getInitialContext();
helloService =
(HelloWorldService)iniCtx.lookup("java:comp/env/service/BpelHello");