[jboss-svn-commits] JBL Code SVN: r37981 - in labs/jbossesb/trunk/product: docs/Programmers_Guide/en-US and 7 other directories.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Wed Apr 4 21:34:24 EDT 2012
Author: tcunning
Date: 2012-04-04 21:34:23 -0400 (Wed, 04 Apr 2012)
New Revision: 37981
Added:
labs/jbossesb/trunk/product/docs/Programmers_Guide/en-US/extras/OOB-Actions/misc-ServiceLoggerAction.xmlt
labs/jbossesb/trunk/product/docs/Programmers_Guide/en-US/extras/OOB-Actions/routing-streamingaggregator.xmlt
labs/jbossesb/trunk/product/docs/Services_Guide/en-US/extras/jbpm/hibernate5.cfg.xml_1.xmlt
labs/jbossesb/trunk/product/docs/Services_Guide/en-US/extras/jbpm/persistence.xml.xmlt
labs/jbossesb/trunk/product/docs/Services_Guide/en-US/jBPM5_Integration.xml
Removed:
labs/jbossesb/trunk/product/samples/quickstarts/bpm5processor/lib/drools-persistence-jpa-5.3.1.Final.jar
labs/jbossesb/trunk/product/samples/quickstarts/bpm5processor/lib/jbpm-persistence-jpa-5.2.0.Final.jar
Modified:
labs/jbossesb/trunk/product/.classpath
labs/jbossesb/trunk/product/build.xml
labs/jbossesb/trunk/product/docs/Programmers_Guide/en-US/Building_and_Using_Services.xml
labs/jbossesb/trunk/product/docs/Programmers_Guide/en-US/OOB-Actions/OOB_Actions_misc.xml
labs/jbossesb/trunk/product/docs/Programmers_Guide/en-US/OOB-Actions/OOB_Actions_routing.xml
labs/jbossesb/trunk/product/docs/Services_Guide/en-US/Services_Guide.xml
labs/jbossesb/trunk/product/docs/Services_Guide/en-US/jBPM_Integration.xml
labs/jbossesb/trunk/product/install/build.xml
labs/jbossesb/trunk/product/services/jbpm5/ivy.xml
Log:
JBESB-3761
Added jbpm5 docs, moved persistence JARs from quickstart to jbpm5.esb, and fixed the classpath.
Modified: labs/jbossesb/trunk/product/.classpath
===================================================================
--- labs/jbossesb/trunk/product/.classpath 2012-04-03 18:26:28 UTC (rev 37980)
+++ labs/jbossesb/trunk/product/.classpath 2012-04-05 01:34:23 UTC (rev 37981)
@@ -1,6 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
<classpathentry excluding="**/.svn/" kind="src" path="rosetta/src"/>
+ <classpathentry excluding="**/.svn/" kind="src" path="services/jbpm5/src/main/java"/>
+ <classpathentry excluding="**/.svn/" kind="src" path="services/jbpm5/src/main/resources"/>
<classpathentry excluding="**/.svn/" kind="src" path="rosetta/tests/src"/>
<classpathentry excluding="**/.svn/" kind="src" path="services/jbossesb/src/main/java"/>
<classpathentry excluding="**/.svn/" kind="src" path="services/jbossesb/src/test/java"/>
Modified: labs/jbossesb/trunk/product/build.xml
===================================================================
--- labs/jbossesb/trunk/product/build.xml 2012-04-03 18:26:28 UTC (rev 37980)
+++ labs/jbossesb/trunk/product/build.xml 2012-04-05 01:34:23 UTC (rev 37981)
@@ -40,7 +40,7 @@
<property name="org.jboss.esb.internal.jar.dest" location="build/jbossesb/lib"/>
<!-- JBoss ESB version -->
- <property name="version" value="4.10"/>
+ <property name="version" value="4.11"/>
<property name="esb.server.name" value="jbossesb-server-${version}"/>
<property name="esbserver.dist.dir" value="${org.jboss.esb.internal.dest}/${esb.server.name}"/>
Modified: labs/jbossesb/trunk/product/docs/Programmers_Guide/en-US/Building_and_Using_Services.xml
===================================================================
--- labs/jbossesb/trunk/product/docs/Programmers_Guide/en-US/Building_and_Using_Services.xml 2012-04-03 18:26:28 UTC (rev 37980)
+++ labs/jbossesb/trunk/product/docs/Programmers_Guide/en-US/Building_and_Using_Services.xml 2012-04-05 01:34:23 UTC (rev 37981)
@@ -694,6 +694,11 @@
<para>
org.jboss.internal.soa.esb.message.filter.EntryExitTimeFilter
</para>
+ </listitem>
+ <listitem>
+ <para>
+ org.jboss.internal.soa.esb.message.filter.ServiceRouteFilter
+ </para>
</listitem>
</itemizedlist>
@@ -759,6 +764,14 @@
(or absence) of the following named entries within the
additional parameters.
</para>
+
+ <para>Note: When the ServiceRouteFilter is added, it still must be configured
+ within a Service, or on a message level. To enable this filter on the
+ service level, add 'recordRoute="true"' to your <service/> definition. If you
+ wish to enable it on a per-message level, add a "service-record-route" property
+ to the message properties and set it to "true". This filter will place information
+ on service entry and service exit within the Message context.
+ </para>
<variablelist><title>Gateway-Generated Message Parameters</title>
@@ -783,6 +796,65 @@
</section>
+<section id="sect-SOA_ESB_Programmers_Guide-Building_and_Using_Services-PipelineInterceptors">
+ <title>
+ Pipeline Interceptors
+ </title>
+
+ <para>
+ As a message flows through the action pipeline, it also might be necessary
+ to intercept the pipeline at different points in the service lifecycle. Pipeline
+ Interceptors have been added in ESB 4.11 that allow a developer to configure an
+ interceptor which will be passed a the service configuration and the message at the
+ start of the service, at the end of the service, at service instantiation, and at
+ the point at which the action pipeline fails due to an Exception.
+ </para>
+
+ <para>
+ The interface org.jboss.soa.esb.listeners.message.PipelineInterceptor has one
+ methods:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ public void processMessage (Message msg, ConfigTree config) which is
+ called at the interception points defined in the jbossesb-properties.xml
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ PipelineInterceptors are defined in the interceptors section of the
+ jbossesb-properties.xml file (typically located in the
+ jbossesb.sar archive) using the following properties:
+ org.jboss.soa.esb.pipeline.failure.interceptors,
+ org.jboss.soa.esb.pipeline.instantiate.interceptors,
+ org.jboss.soa.esb.pipeline.start.interceptors,
+ org.jboss.soa.esb.pipeline.end.interceptors
+ </para>
+
+ <note>
+ <para>
+ You will need to place any changes to your
+ jbossesb-properties.xml file on each ESB instance that is
+ deployed in your environment. This will ensure that all ESB
+ instances can process the same meta-data.
+ </para>
+ </note>
+
+ <para>
+ JBossESB ships with only a org.jboss.soa.esb.listeners.message.GenericPipelineInterceptor,
+ which prints the message and demonstrates the general concept. It is up to the developer
+ to provide the concrete implementation to use.
+ </para>
+
+
+</section>
+
+
<section id="sect-SOA_ESB_Programmers_Guide-Building_and_Using_Services-What_is_a_Service">
<title>
Modified: labs/jbossesb/trunk/product/docs/Programmers_Guide/en-US/OOB-Actions/OOB_Actions_misc.xml
===================================================================
--- labs/jbossesb/trunk/product/docs/Programmers_Guide/en-US/OOB-Actions/OOB_Actions_misc.xml 2012-04-03 18:26:28 UTC (rev 37980)
+++ labs/jbossesb/trunk/product/docs/Programmers_Guide/en-US/OOB-Actions/OOB_Actions_misc.xml 2012-04-05 01:34:23 UTC (rev 37981)
@@ -115,4 +115,61 @@
</example>
</section>
+
+ <section>
+ <title>ServiceLoggerAction</title>
+ <para>
+ Simple action that logs custom text and possibly the message to a logger using the
+ "<service-category>.<service-name<" appender. This action differs from LogAction
+ in that it allows you to set LogLevelAction on a per service basis, rather
+ than on a per-action basis, and that it allows you to log custom text.
+ Debug level setting will result in the ESB message being output.
+ Trace level setting will result in the output of the message payload
+ </para>
+
+ <para>
+ Logs custom text or the message using an appender.
+ </para>
+
+ <informaltable>
+ <tgroup align="left" cols="2" colsep="1" rowsep="1">
+ <colspec colwidth="1*"/>
+ <colspec colwidth="5*"/>
+ <tbody>
+ <row>
+ <entry>Input Type</entry>
+ <entry><classname>java.lang.String</classname></entry>
+ </row>
+ <row>
+ <entry>Class</entry>
+ <entry><classname>org.jboss.soa.esb.actions.ServiceLoggerAction</classname></entry>
+ </row>
+ <row>
+ <entry>Properties</entry>
+ <entry>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <property>text</property> - A message prefix. <literal>Required</literal>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <property>get-payload-location</property> - True or False value which specifies
+ whether the payload location should be logged in Trace
+ </para>
+ </listitem>
+ </itemizedlist>
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+
+ <example>
+ <title>ServiceLoggerAction</title>
+ <programlisting language="XML" role="XML"><xi:include href="../extras/OOB-Actions/misc-SystemPrintln.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+ </example>
+ </section>
+
</section>
Modified: labs/jbossesb/trunk/product/docs/Programmers_Guide/en-US/OOB-Actions/OOB_Actions_routing.xml
===================================================================
--- labs/jbossesb/trunk/product/docs/Programmers_Guide/en-US/OOB-Actions/OOB_Actions_routing.xml 2012-04-03 18:26:28 UTC (rev 37980)
+++ labs/jbossesb/trunk/product/docs/Programmers_Guide/en-US/OOB-Actions/OOB_Actions_routing.xml 2012-04-05 01:34:23 UTC (rev 37981)
@@ -81,6 +81,83 @@
</section>
+ <section id="section-StreamingAggregator">
+ <title>Streaming Aggregator</title>
+ <informaltable>
+ <tgroup align="left" cols="2" colsep="1" rowsep="1">
+ <colspec colwidth="1*"/>
+ <colspec colwidth="5*"/>
+ <tbody>
+ <row>
+ <entry>Class</entry>
+ <entry><classname>org.jboss.soa.esb.actions.StreamingAggregator</classname></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+
+ <para>
+ Streaming Message aggregation action. An implementation of the Aggregator
+ Enterprise Integration Pattern, see
+ <ulink url="http://www.enterpriseintegrationpatterns.com/Aggregator.html" />.
+ </para>
+
+ <para>
+ The Streaming Aggregator, new in ESB 4.11, is an improved message aggregation action.
+ Unlike the previous aggregator, the streaming aggregator does not require all messages
+ to have complete aggregation details - messages must have the message order number and a
+ unique aggregation id, but all messages do not need to specify how many messages will be
+ aggregated in each message. The number of messages aggregated can be sent in a subsequent
+ message, which is a performance improvement when dealing with extremely large files which
+ need to be line counted or parse, or Smooks fragments which need to be split.</para>
+
+ <para>Data is set on the message as a property called "Aggregate.AggregateDetails" which sets
+ should contain a org.jboss.soa.esb.actions.aggregator.AggregateDetails object.
+ </para>
+
+ <para>
+ The data has the following format:
+ </para>
+ <programlisting>[SeriesUUID] ":" [message-sequence] ":" [sequence-count]</programlisting>
+
+
+ <para>
+ If all the messages have been received by the Streaming Aggregator, it returns a new
+ Message containing all the messages as part of the Message.Attachment list
+ (unnamed), otherwise the action returns null.
+ </para>
+
+ <table>
+ <title>Aggregator Properties</title>
+ <tgroup cols="3" colsep="1" rowsep="1">
+ <colspec colwidth="2*"/>
+ <colspec colwidth="5*"/>
+ <colspec colwidth="1*"/>
+ <thead>
+ <row><entry>Property</entry><entry>Description</entry><entry>Required</entry></row>
+ </thead>
+ <tbody>
+ <row>
+ <entry><property>timeoutInMillis</property></entry>
+ <entry>
+ <para>
+ Timeout time in milliseconds before the aggregation process times out.
+ </para>
+ </entry>
+ <entry>No</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ <example>
+ <title>Sample Configuration</title>
+ <programlisting language="XML" role="XML"><xi:include href="../extras/OOB-Actions/routing-streamingaggregator.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+ </example>
+
+ </section>
+
+
<section id="section-EchoRouter">
<title>EchoRouter</title>
<para>
Added: labs/jbossesb/trunk/product/docs/Programmers_Guide/en-US/extras/OOB-Actions/misc-ServiceLoggerAction.xmlt
===================================================================
--- labs/jbossesb/trunk/product/docs/Programmers_Guide/en-US/extras/OOB-Actions/misc-ServiceLoggerAction.xmlt (rev 0)
+++ labs/jbossesb/trunk/product/docs/Programmers_Guide/en-US/extras/OOB-Actions/misc-ServiceLoggerAction.xmlt 2012-04-05 01:34:23 UTC (rev 37981)
@@ -0,0 +1,4 @@
+<action name="servicelogger" class="org.jboss.soa.esb.actions.ServiceLoggerAction">
+ <property name="text" value="Reached here"/><br/>
+ <property name="get-payload-location" value="true"/>
+</action>
Added: labs/jbossesb/trunk/product/docs/Programmers_Guide/en-US/extras/OOB-Actions/routing-streamingaggregator.xmlt
===================================================================
--- labs/jbossesb/trunk/product/docs/Programmers_Guide/en-US/extras/OOB-Actions/routing-streamingaggregator.xmlt (rev 0)
+++ labs/jbossesb/trunk/product/docs/Programmers_Guide/en-US/extras/OOB-Actions/routing-streamingaggregator.xmlt 2012-04-05 01:34:23 UTC (rev 37981)
@@ -0,0 +1,3 @@
+<action class="org.jboss.soa.esb.actions.StreamingAggregator" name="Aggregator">
+ <property name="timeoutInMillies" value="60000"/>
+</action>
Modified: labs/jbossesb/trunk/product/docs/Services_Guide/en-US/Services_Guide.xml
===================================================================
--- labs/jbossesb/trunk/product/docs/Services_Guide/en-US/Services_Guide.xml 2012-04-03 18:26:28 UTC (rev 37980)
+++ labs/jbossesb/trunk/product/docs/Services_Guide/en-US/Services_Guide.xml 2012-04-05 01:34:23 UTC (rev 37981)
@@ -32,6 +32,7 @@
<xi:include href="Message_Transformation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="jBPM_Integration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="jBPM5_Integration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Service_Orchestration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="The_Message_Store.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Security.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
Added: labs/jbossesb/trunk/product/docs/Services_Guide/en-US/extras/jbpm/hibernate5.cfg.xml_1.xmlt
===================================================================
--- labs/jbossesb/trunk/product/docs/Services_Guide/en-US/extras/jbpm/hibernate5.cfg.xml_1.xmlt (rev 0)
+++ labs/jbossesb/trunk/product/docs/Services_Guide/en-US/extras/jbpm/hibernate5.cfg.xml_1.xmlt 2012-04-05 01:34:23 UTC (rev 37981)
@@ -0,0 +1,7 @@
+<!-- JTA transaction properties (begin) ===
+ ==== JTA transaction properties (end) -->
+<property name="hibernate.transaction.factory_class">
+ org.hibernate.transaction.JTATransactionFactory</property>
+
+<property name="hibernate.transaction.manager_lookup_class">
+ org.hibernate.transaction.JBossTransactionManagerLookup</property>
\ No newline at end of file
Added: labs/jbossesb/trunk/product/docs/Services_Guide/en-US/extras/jbpm/persistence.xml.xmlt
===================================================================
--- labs/jbossesb/trunk/product/docs/Services_Guide/en-US/extras/jbpm/persistence.xml.xmlt (rev 0)
+++ labs/jbossesb/trunk/product/docs/Services_Guide/en-US/extras/jbpm/persistence.xml.xmlt 2012-04-05 01:34:23 UTC (rev 37981)
@@ -0,0 +1,26 @@
+<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
+<persistence version="1.0"
+ xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
+ http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd
+ http://java.sun.com/xml/ns/persistence/orm
+ http://java.sun.com/xml/ns/persistence/orm_1_0.xsd"
+ xmlns:orm="http://java.sun.com/xml/ns/persistence/orm"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xmlns="http://java.sun.com/xml/ns/persistence">
+
+ <persistence-unit name="jbpm5Persistence.jpa" transaction-type="JTA">
+ <provider>org.hibernate.ejb.HibernatePersistence</provider>
+ <jta-data-source>java:jboss/datasources/jbpm5DS</jta-data-source>
+
+ <mapping-file>META-INF/JBPMorm.xml</mapping-file>
+ <class>org.jbpm.persistence.processinstance.ProcessInstanceInfo</class>
+ <class>org.drools.persistence.info.SessionInfo</class>
+ <class>org.drools.persistence.info.WorkItemInfo</class>
+ <properties>
+ <property name="hibernate.dialect" value="org.hibernate.dialect.MySQL5Dialect"/>
+ <property name="hibernate.hbm2ddl.auto" value="update"/>
+ <!-- for AS5 -->
+ <property name="hibernate.transaction.manager_lookup_class" value="org.hibernate.transaction.JBossTransactionManagerLookup" />
+ </properties>
+ </persistence-unit>
+</persistence>
Added: labs/jbossesb/trunk/product/docs/Services_Guide/en-US/jBPM5_Integration.xml
===================================================================
--- labs/jbossesb/trunk/product/docs/Services_Guide/en-US/jBPM5_Integration.xml (rev 0)
+++ labs/jbossesb/trunk/product/docs/Services_Guide/en-US/jBPM5_Integration.xml 2012-04-05 01:34:23 UTC (rev 37981)
@@ -0,0 +1,402 @@
+<?xml version='1.0'?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
+"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Services_Guide.ent">
+%BOOK_ENTITIES;
+]>
+
+<chapter>
+ <title>
+ jBPM 5 Integration
+ </title>
+
+ <section>
+ <title>
+ Integration Configuration
+ </title>
+
+ <para>
+ The jbpm5.esb deployment that ships with the ESB includes the
+ jBPM 5 runtime, a datasource, a hibernate configuration, and a JPA
+ persistence configuration. The datasource is configured by default to use
+ h2 as a backend database, and is used to persist session and process information.
+ </para>
+
+ <para>
+ In production you will want change from h2 to a production strength database.
+ All jbpm5.esb deployments should share the same database instance so that the
+ various ESB nodes have access to the same processes definitions and instances.
+ </para>
+
+ <para>
+ The jBPM 5 GWT console is a web application that is not included, but that can be
+ optionally installed through the jBPM 5 installer. Please use the jbpm-5.2.0.Final
+ installer as this is the version that has been tested against the ESB. You may
+ need to make minor changes to the configuration of the JBPM 5 GWT console - you will want
+ to change the to change the "context-root" in WEB-INF/jboss-web.xml from 'jbpm-console'
+ to 'jbpm5-console' so that it does not conflict with the jbpm 3 version console which ships
+ by default in the ESB.
+ </para>
+
+ <para>
+ Please check the jBPM 5 documentation to change the
+ security settings for this application, which will involve change
+ some settings in the conf/login-config.xml. The console can be used
+ for deploying and monitoring jBPM processes, but it can also be
+ used for human task management. For different users, a
+ customized task list will be shown and they can administer those
+ tasks.
+ </para>
+
+ <para>
+ The jbpm5.esb/META-INF directory contains the deployment.xml and the
+ jboss-esb.xml. The deployment.xml specifies the resources this esb
+ archive depends on:
+ </para>
+
+<programlisting language="XML" role="XML"><xi:include href="extras/jbpm/jbpm5_deployment.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>
+
+ </section>
+
+ <section>
+ <title>
+ jBPM 5 configuration
+ </title>
+
+ <para>
+ The configuration of jBPM itself is managed by two files, the
+ persistence.xml and the hibernate.cfg.xml.
+ </para>
+
+ <para>
+ By default the persistence.xml is set to use the JTA transacion
+ manager, as defined in the section:
+ </para>
+
+
+ <programlisting language="XML" role="XML"><xi:include href="extras/jbpm/persistence.xml.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>
+
+
+ <para>
+ Other settings are left to the default jBPM settings.
+ </para>
+
+ <para>
+ Hibernate is used to create the database schema.
+ </para>
+
+ </section>
+
+ <section>
+ <title>
+ Creation and Deployment of a Process Definition
+ </title>
+
+ <para>
+ To create a Process Definition we recommend using the Eclipse BPMN
+ 2.0 plugin. The jBPM 5.2.0.Final installer will download and configure a complete
+ Eclipse installation with the plugin.
+ </para>
+
+ <para>
+ The graphical editor allows you to create a process definition
+ visually. Nodes and transitions between nodes can be added,
+ modified or removed. The process definition saves as an XML
+ document which can be stored on a file system and deployed to a
+ jBPM instance (database). Each time you deploy the process instance
+ jBPM will version it and will keep the older copies. This allows
+ processes that are in flight to complete using the process instance
+ they were started on. New process instances will use the latest
+ version of the process definition.
+ </para>
+
+ </section>
+
+
+
+ <section>
+ <title>
+ JBossESB to jBPM
+ </title>
+
+ <para>
+ JBossESB can make calls into jBPM 5 using the Bpm5Processor action.
+ This action uses the jBPM 5 command API to make calls into jBPM. The
+ following jBPM commands have been implemented:
+ </para>
+
+<table>
+ <title>jBPM 5 commands</title>
+ <tgroup cols="2" colsep="1" rowsep="1">
+ <colspec colwidth="9*"/>
+ <colspec colwidth="9*"/>
+ <thead>
+ <row><entry>Command</entry><entry>Description</entry></row>
+ </thead>
+ <tbody>
+
+ <row>
+ <entry>
+ <command>startProcess</command>
+ </entry>
+ <entry>
+ <para>
+ Start a new ProcessInstance given a process definition
+ that was already deployed to jBPM. </para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <command>signalEvent</command>
+ </entry>
+ <entry>
+ <para>
+ Signal an already-started process that an event has occurred.
+ </para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <command>abortProcessInstance</command>
+ </entry>
+ <entry>
+ <para>
+ Cancel a ProcessInstance. i.e. when an event comes in
+ which should result in the cancellation of the entire
+ ProcessInstance. This action requires some jBPM context
+ variables to be set on the message, in particular the
+ ProcessInstance Id. Details on that are discussed later.
+ </para>
+ </entry>
+ </row>
+
+ </tbody>
+ </tgroup>
+</table>
+
+ <para>
+ The configuration for this action in the jboss-esb.xml looks like
+ </para>
+
+
+
+<programlisting language="XML" role="XML"><xi:include href="extras/jbpm/bpm_processor_conf_1.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>
+
+
+
+ <para>
+ There are two required action attributes:
+ </para>
+
+ <orderedlist>
+ <listitem>
+ <para>
+ name
+ </para>
+
+ <para>
+ Required attribute. You are free to use any value for
+ the name attribute as long as it is unique in the
+ action pipeline.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ class
+ </para>
+
+ <para>
+ Required attribute. This attributes needs to be set to
+ “org.jboss.soa.esb.services.jbpm5.actions.Bpm5Processor”
+ </para>
+ </listitem>
+ </orderedlist>
+
+ <para>
+ Furthermore one can configure the following configuration properties:
+ </para>
+
+<table>
+ <title>Configuration Properties</title>
+ <tgroup cols="3" colsep="1" rowsep="1">
+ <colspec colwidth="5*"/>
+ <colspec colwidth="9*"/>
+ <colspec colwidth="2*"/>
+ <thead>
+ <row><entry>Property</entry><entry>Description</entry><entry>Required?</entry></row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <property>process-action</property>
+ </entry>
+ <entry>
+ <para>
+ Needs to be one of:
+ startProcess, signalEvent, or abortProcessInstance.
+ </para>
+ </entry>
+ <entry>
+ <para>
+ Yes
+ </para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <property>process-definition-name</property>
+ </entry>
+ <entry>
+ <para>
+ Required property. The value
+ of this property should reference a process definition
+ that is already deployed to jBPM and of which you want
+ to create a new instance.
+ </para>
+ </entry>
+ <entry>
+ <para>
+ Yes
+ </para>
+ </entry>
+ </row>
+
+
+ <row>
+ <entry>
+ <property>process-id</property>
+ </entry>
+ <entry>
+ <para>
+ The value of this property should reference a process
+ definition id in jBPM of which you want to create a
+ new instance.
+ </para>
+ </entry>
+ <entry>
+ <para>
+ Yes
+ </para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <property>esbToBpmVars</property>
+ </entry>
+ <entry>
+
+
+ <para>
+ optional property. This property defines a list of
+ variables that need to be extracted from the EsbMessage and set
+ into jBPM context for the particular process instance. The list
+ consists of mapping elements. Each mapping element can have the
+ following attributes:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+
+ <para>
+ esb
+ </para>
+
+ <para>
+ required attribute which can contain an
+ MVEL expression to extract a value anywhere
+ from the EsbMessage.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>bpm</para>
+ <para>
+ optional attribute
+ containing the name
+ which be used on the
+ jBPM side. If omitted
+ the esb name is used.
+ </para>
+ </listitem>
+ <listitem>
+ <para>value</para>
+ <para>
+ optional attribute
+ which can hold a
+ hard coded value.
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ </entry>
+ <entry>
+ <para>
+ No
+ </para>
+ </entry>
+ </row>
+
+ </tbody>
+ </tgroup>
+ </table>
+
+ <para>
+ Finally some variables can be set in context of the
+ EsbMessage:
+ </para>
+
+<table>
+ <title>Body Configuration Properties</title>
+ <tgroup cols="3" colsep="1" rowsep="1">
+ <colspec colwidth="5*"/>
+ <colspec colwidth="9*"/>
+ <colspec colwidth="2*"/>
+ <thead>
+ <row><entry>Property</entry><entry>Description</entry><entry>Required?</entry></row>
+ </thead>
+ <tbody>
+
+ <row>
+ <entry>
+ <property>jbpm5-processinstance-id</property>
+ </entry>
+ <entry>
+ <para>
+ ESB context property that applies to
+ the signalEvent and abortProcessInstance commands.
+ </para>
+ </entry>
+ <entry>
+ <para>
+ Yes
+ </para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <property>jbpm5-session-id</property>
+ </entry>
+ <entry>
+ <para>
+ ESB context property that tells the action what session to load.
+ </para>
+ </entry>
+ <entry>
+ <para>
+ Yes
+ </para>
+ </entry>
+ </row>
+
+ </tbody>
+ </tgroup>
+ </table>
+
+</section>
+ </chapter>
Modified: labs/jbossesb/trunk/product/docs/Services_Guide/en-US/jBPM_Integration.xml
===================================================================
--- labs/jbossesb/trunk/product/docs/Services_Guide/en-US/jBPM_Integration.xml 2012-04-03 18:26:28 UTC (rev 37980)
+++ labs/jbossesb/trunk/product/docs/Services_Guide/en-US/jBPM_Integration.xml 2012-04-05 01:34:23 UTC (rev 37981)
@@ -7,7 +7,7 @@
<chapter>
<title>
- jBPM Integration
+ jBPM 3 Integration
</title>
Modified: labs/jbossesb/trunk/product/install/build.xml
===================================================================
--- labs/jbossesb/trunk/product/install/build.xml 2012-04-03 18:26:28 UTC (rev 37980)
+++ labs/jbossesb/trunk/product/install/build.xml 2012-04-05 01:34:23 UTC (rev 37981)
@@ -409,7 +409,7 @@
</copy>
<copy todir="${deploy.dir}"
- file="${product.dir}/build/juddiv3.war"/>
+ file="${org.jboss.esb.dist.lib}/juddiv3.war"/>
<copy tofile="${deploy.dir}/jbossesb.sar/META-INF/jboss-service.xml" file="${basedir}/jboss-service-jbossas5.xml" overwrite="true"/>
Deleted: labs/jbossesb/trunk/product/samples/quickstarts/bpm5processor/lib/drools-persistence-jpa-5.3.1.Final.jar
===================================================================
(Binary files differ)
Deleted: labs/jbossesb/trunk/product/samples/quickstarts/bpm5processor/lib/jbpm-persistence-jpa-5.2.0.Final.jar
===================================================================
(Binary files differ)
Modified: labs/jbossesb/trunk/product/services/jbpm5/ivy.xml
===================================================================
--- labs/jbossesb/trunk/product/services/jbpm5/ivy.xml 2012-04-03 18:26:28 UTC (rev 37980)
+++ labs/jbossesb/trunk/product/services/jbpm5/ivy.xml 2012-04-05 01:34:23 UTC (rev 37981)
@@ -7,8 +7,9 @@
<dependency org="org.jbpm" name="jbpm-flow-builder" rev="5.2.0.Final" transitive="false"/>
<dependency org="org.jbpm" name="jbpm-flow" rev="5.2.0.Final" transitive
="false"/>
+ <dependency org="org.jbpm" name="jbpm-persistence-jpa" rev="5.2.0.Final" transitive="false"/>
+ <dependency org="org.drools" name="drools-persistence-jpa" rev="5.3.1.Final" transitive="false"/>
-
<dependency org="org.drools" name="drools-core" rev="5.3.1.Final" transitive="false"/>
<dependency org="org.drools" name="knowledge-api" rev="5.3.1.Final" transitive="false"/>
</dependencies>
More information about the jboss-svn-commits
mailing list