[esb-issues] [JBoss JIRA] Commented: (JBESB-2239) StartProcessInstanceCommand: Return token id/process instance id

[Kevin Conner (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBESB-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12443042#action_12443042 ] 

Kevin Conner commented on JBESB-2239:
-------------------------------------

We cannot clean anything up in the EPR as it is intended to be an opaque structure.

As for the token/process instance id that was deliberately removed to prevent anyone other than jBPM from driving the process.

If you have a use case for this, can you raise it on the forums?  We can discuss it and decide what is appropriate.

> 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