[
https://jira.jboss.org/jira/browse/JBESB-2239?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2239:
-------------------------------------
Unfortunately, just because something exists doesn't mean that they should exist.
The reworked integration was intended to remove many of those including the, extremely
broken, signal command. Unfortunately this did not happen.
If someone creates a jBPM process then it is the jBPM process that assumes responsibility
for control, that is the whole point of the orchestration.
As I said earlier, this is not a discussion forum. Take this to the forums and we can
discuss the requirements and *then* decide to create JIRAs.
StartProcessInstanceCommand: Return token id/process instance id
----------------------------------------------------------------
Key: JBESB-2239
URL:
https://jira.jboss.org/jira/browse/JBESB-2239
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Process flow
Affects Versions: 4.4 CP1
Reporter: Burr Sutter
A very common request is to have the BpmProcessor action return a token/process instance
id. Perhaps in the
<action name="start_a_new_process_instance"
class="org.jboss.soa.esb.services.jbpm.actions.BpmProcessor">
<property name="command"
value="StartProcessInstanceCommand" />
<property name="process-definition-name"
value="bpm_orchestration3Process"/>
<property name="key" value="businessKey"/>
<property name="esbToBpmVars">
<mapping esb="BODY_CONTENT" bpm="theBody"
/>
<mapping esb="contentsAsString"
bpm="theData" />
</property>
</action>
Perhaps we could do that as variable mapping.
It has also be requested that we clean up the callback EPR XML. It is a rather large
chunk of information currently
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira