[
http://jira.jboss.com/jira/browse/JBESB-1512?page=all ]
Kevin Conner closed JBESB-1512.
-------------------------------
Resolution: Rejected
The use case was bpm_orchestration3 but this case is no longer supported by the ESB.
This case can now be handled completely within jBPM with ESB providing services through
the new async mechanism.
Need a way of determining jbpmTokenId
-------------------------------------
Key: JBESB-1512
URL:
http://jira.jboss.com/jira/browse/JBESB-1512
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Process flow
Reporter: Tom Cunningham
Fix For: 4.2.1 CP1
Talked to Kurt about this one - the jbpmTokenId is required to signal a process, but it
is hard to get. Currently, the only way to determine the jbpmTokenId is to use the
jbpmConsole. Two options for improving this would be :
1. Have jBPM call back into a service so we can obtain the id that way
or
2. Have the jBPM deploy command return the ID
--
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