[jbpm-commits] JBoss JBPM SVN: r4378 - jbpm4/trunk/modules/userguide/src/main/docbook/en/modules.

do-not-reply at jboss.org do-not-reply at jboss.org
Wed Apr 1 12:09:12 EDT 2009


Author: tom.baeyens at jboss.com
Date: 2009-04-01 12:09:12 -0400 (Wed, 01 Apr 2009)
New Revision: 4378

Modified:
   jbpm4/trunk/modules/userguide/src/main/docbook/en/modules/ch04-Services.xml
Log:
documentation update to repository service

Modified: jbpm4/trunk/modules/userguide/src/main/docbook/en/modules/ch04-Services.xml
===================================================================
--- jbpm4/trunk/modules/userguide/src/main/docbook/en/modules/ch04-Services.xml	2009-04-01 15:22:15 UTC (rev 4377)
+++ jbpm4/trunk/modules/userguide/src/main/docbook/en/modules/ch04-Services.xml	2009-04-01 16:09:12 UTC (rev 4378)
@@ -38,10 +38,11 @@
     can be obtained:
     </para>
     
-    <programlisting><emphasis role="bold">ProcessService</emphasis> processService = processEngine.getProcessService();
+    <programlisting><emphasis role="bold">RepositoryService</emphasis> repositoryService = processEngine.getRepositoryService();
 <emphasis role="bold">ExecutionService</emphasis> executionService = processEngine.getExecutionService();
-<emphasis role="bold">ManagementService</emphasis> managementService = processEngine.getManagementService();
-<emphasis role="bold">TaskService</emphasis> taskService = processEngine.getTaskService();</programlisting>
+<emphasis role="bold">TaskService</emphasis> taskService = processEngine.getTaskService();
+<emphasis role="bold">HistoryService</emphasis> historyService = processEngine.getHistoryService();
+<emphasis role="bold">ManagementService</emphasis> managementService = processEngine.getManagementService();</programlisting>
 
     <para>Process engine objects defined in the configuration can also be retrieved by 
     type (<literal>processEngine.get(Class&lt;T&gt;)</literal>) 
@@ -51,14 +52,17 @@
 
   <section id="deployingaprocess">
     <title>Deploying a process</title>
-    <para>The <literal>ProcessService</literal> groups all methods that access 
-    the repository of process definitions.
+    <para>The <literal>RepositoryService</literal> groups all methods to manage 
+    the repository of deployments.  Each deployment is composed of a set of named 
+    resources.  The content of each resource is a byte array.  One type of resources
+    is a jPDL process file.  Potentially multiple process files can be deployed 
+    together with resources like forms and other resources. 
     </para>
-    <para>A jPDL process file like e.g. <literal>order.jpdl.xml</literal> that is 
-    accessible as a resource on the classpath can be deployed programmatically with the 
-    <literal>ProcessService</literal> like this:
+    <para>jPDL process files are recognized by their extension <literal>.jpdl.xml</literal>.
+    In this first example, we'll deploy a process resource from the classpath
+    with the <literal>RepositoryService</literal> like this:
     </para>
-    <programlisting>processService.createDeployment()
+    <programlisting>repositoryService.createDeployment()
     .addResource("order.jpdl.xml")
     .deploy();</programlisting>
     <para>Analogue to the <literal>addResource</literal> method above, the source of 




More information about the jbpm-commits mailing list