[
http://jira.jboss.com/jira/browse/JBSEAM-2951?page=comments#action_12412176 ]
Norman Richards commented on JBSEAM-2951:
-----------------------------------------
I think the real sticky point here is in providing functionality on the component that
isn't exposed via annotations or any of our other process control mechanisms. I
really don't understand the use case well enough to know if we need to expose any of
this behavior or to understand the implications in a Seam app of the user manually mucking
with the process. Certainly Seam cannot mirror every piece of JBPM functionality and at
some point if the user needs to do something really tricky they should probably be doing
it themselves. Since you seem to think this is definitely something that needs to happen,
I'll add the method in.
Add ability to start jBPM in the wait-state instead of only the
start-state
---------------------------------------------------------------------------
Key: JBSEAM-2951
URL:
http://jira.jboss.com/jira/browse/JBSEAM-2951
Project: Seam
Issue Type: Feature Request
Components: BPM
Reporter: Samuel Mendenhall
Assigned To: Norman Richards
Priority: Minor
"jBPM itself does work as stated in the *jBPM docs*, i.e. start-state behaves as a
wait state. It is Seam who signals the process instance right after it is created,
effectively disabling the wait behavior of the start-state.
The intent of giving the start-state a wait behavior is to allow the caller to set
variables or complete a user task prior to executing any action in the process.
Seam should offer a way to create a process instance without signaling it right away.
Changing the behavior to leave the signal() out would break existing applications who
assume that the process instance immediately moves to the next step. To deal with this,
Seam could add a createProcess(ProcessDefinition, boolean) method to the BusinessProcess
class. The boolean parameter tells whether the process instance is to be signaled."
--Alejandro Guizar
--
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