[
http://jira.jboss.com/jira/browse/JBESB-1422?page=comments#action_12394530 ]
Kevin Conner commented on JBESB-1422:
-------------------------------------
Jirka, there are two ways in which a process can be started and the one chosen depends on
the definition of the process which is being created.
The two ESB commands used for creating and starting a process are
- NewProcessInstanceCommand
This command creates a process which does not require a subsequent signal. The reasons
for could be that the
start state has been defined as a deliberate wait state or that there is an initial
state specified in the process definition
- StartProcessInstanceCommand
This command creates a process which *does* require a signal and the specification of
the initial transition.
Whichever command is chosen, we would expect the jBPM process to be active once that
command has executed and would therefore have no need of propagating the token/process
ids. Once the jBPM process is active we would expect it to drive all interactions.
CreateNewProcess does not propagate token/processId
---------------------------------------------------
Key: JBESB-1422
URL:
http://jira.jboss.com/jira/browse/JBESB-1422
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Process flow
Affects Versions: 4.2.1 CP1
Environment: FC7/PostgreSQL
Reporter: Jiri Pechanec
Assigned To: Kurt Stam
Priority: Critical
Fix For: 4.2.1 CP1
When CreateNew Process command is called it does not propagate anywhere
processId/tokenId. It means that it is not possible to send signal to created process.
--
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