[ https://issues.jboss.org/browse/JBESB-3830?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated JBESB-3830: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=839327 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBESB-3830?page=com.atlassian.jira.plugin... ] Tom Cunningham commented on JBESB-3830: --------------------------------------- The jbpm3 integration contained correlation checks to see if the token was at the right node and that it was still the same invocation of that node before signaling an event. These checks should be added to the jbpm5 integration. Also, the jbpm3 integration contained an ActionHandler, which sent a message and suspended execution of the action while awaiting a response. We should add a second WorkItemHandler that is equivalent to this. The important checks in the jBPM3 integration are - make sure token is on the correct node (hasn't moved on in the process flow) - make sure that this is still the same invocation of that node (counter associated with node) to prevent interference from loops otherwise signalling the token could interfere with the current process execution. See CallbackCommand for details. Taking a quick look at the jBPM5 integration would suggest that it will result in similar issues. There are also a couple of other issues - ESBServiceWorkItemHandler sends a message to the ESB but then completes the workitem. In jBPM3 we had two jBPM actions for communicating with the ESB - EsbNotifier - send a message without requiring a response - EsbActionHandler - send a message and suspend execution of the action while awaiting a response. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBESB-3830?page=com.atlassian.jira.plugin... ] Tom Cunningham updated JBESB-3830: ---------------------------------- Fix Version/s: 4.12 Affects Version/s: 4.11 Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=839327 (was: https://bugzilla.redhat.com/show_bug.cgi?id=839327) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBESB-3830?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBESB-3830: ------------------------------------------------ Ken Johnson <kejohnso(a)redhat.com&gt; made a comment on [bug 839327|https://bugzilla.redhat.com/show_bug.cgi?id=839327] Gah! Can this be implemented in a roll-up patch? It's too late to back this feature off to tech preview status and we can't delay the release any longer to get it in as a GA feature. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBESB-3830?page=com.atlassian.jira.plugin... ] Tom Cunningham closed JBESB-3830. --------------------------------- -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira