Big oops. I thought the ProcessInstance fired it upon its construction:
// fire the process start event
| if (rootToken.getNode()!=null) {
| ExecutionContext executionContext = new ExecutionContext(rootToken);
| processDefinition.fireEvent(Event.EVENTTYPE_PROCESS_START,
executionContext);
| }
At this point the root token will point to the start node if there is one.
However, BPEL processes do not have a start node, as they could potentially
have multiple start activities (i.e. < receive>s with createInstance="yes").
Thanks for reporting the problem. I'll just fire the event in
BpelDefinition.createProcessInstance() rather than .startProcessInstance() to
be more consistent with the jBPM behavior. Could you open a JIRA issue for
tracking purposes?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3921579#3921579
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3921579
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
