[
http://jira.jboss.com/jira/browse/JBESB-364?page=all ]
Esteban Schifman resolved JBESB-364.
------------------------------------
Resolution: Done
See the following classes:
org.jboss.soa.esb.util.AbstractCommandVehicle - to help standardize Command
messages in ESB
org.jboss.soa.esb.jbpm.CommandVehicle - extends the above, specialized
for jBPM interaction
org.jboss.soa.esb.actions.jbpm.CommandInterpreter- ESB action class that invokes jBPM
methods when a Command message is received
org.jboss.soa.esb.services.jbpm.BaseActionHandler- Base jBPM ActionHandler that eases the
task of sending messages to ESB services using the CommandVehicle mentioned above
jBPM integration
----------------
Key: JBESB-364
URL:
http://jira.jboss.com/jira/browse/JBESB-364
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: BPM
Affects Versions: 4.0 CR2
Reporter: Mark Little
Assigned To: Esteban Schifman
Priority: Critical
Fix For: 4.0 Maintenance Pack 1
Adding a jBPM Action that knows how to invoke a service, an ESB action that knows how to
start a new process instance or via the tokenid in the message header, signal a process
instance.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira