9:02 a.m.
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
3:22 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2239) StartProcessInstanceCommand: Return token id/process instance id
[
https://jira.jboss.org/jira/browse/JBESB-2239?page=com.atlassian.jira.plu...
]
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
6:37 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-2239) StartProcessInstanceCommand: Return token id/process instance id
[
https://jira.jboss.org/jira/browse/JBESB-2239?page=com.atlassian.jira.plu...
]
Aaron Pestel commented on JBESB-2239:
-------------------------------------
Would seem that the BpmProcessor action itself shows the need for returning a
token/process id. It seems the other BpmProcessor commands (SignalCommand,
CancelProcessInstanceCommand, and setProcessInstanceVariables) need to specify a token ID
or process instance ID
(http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.GA/html-single/Pr...).
If someone uses the ESB to kick off a process instance and they also want to use the ESB
to be able to cancel that same process. If the ESB client that kicks off the process
doesn't get the process ID returned, it will be difficult for that client to cancel
the process that he just created. The non-create/start commands on BpmProcessor seem
pretty useless if the create/start commands can't return a process instance id or
token id.
In addition to this is the even more common case I run into where the customer (NAVTEQ
most recently) want to use BPM for service orchestration. So, client invokes a service on
the ESB and that ESB service needs to synchronously kick off the orchestration of other
services, aggregate a result, and return it to the original client.
I've been telling folks to just not even use BpmProcessor and to implement their own
custom action instead that invokes/controls the BPM process. I see many more real life
use cases for a synchronous BpmProcessor than an asynchronous BpmProcessor.
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
11:22 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-2239) StartProcessInstanceCommand: Return token id/process instance id
[
https://jira.jboss.org/jira/browse/JBESB-2239?page=com.atlassian.jira.plu...
]
Aaron Pestel commented on JBESB-2239:
-------------------------------------
If this action were updated to support synchronous use, it would be nice to generically
support "bpmToEsbVars" in addition to "esbToBpmVars" to be consistent
with the way things are done when jBPM invokes an ESB service.
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
3:44 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2239) StartProcessInstanceCommand: Return token id/process instance id
[
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
3:46 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-2239) StartProcessInstanceCommand: Return token id/process instance id
[
https://jira.jboss.org/jira/browse/JBESB-2239?page=com.atlassian.jira.plu...
]
Kevin Conner closed JBESB-2239.
-------------------------------
Resolution: Rejected
This is being used as a design discussion so I am rejecting it until we have a better
understanding of the requirements.
This should be happening on the forums.
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
5866
days inactive
5869
days old
5 comments
3 participants
participants (3)
-
Aaron Pestel (JIRA) -
Burr Sutter (JIRA)
-
Kevin Conner (JIRA)