[
https://jira.jboss.org/jira/browse/GPD-298?page=com.atlassian.jira.plugin...
]
Koen Aers commented on GPD-298:
-------------------------------
I believe that the problem is in the implementation of the EsbNotifier (or
EsbActionHandler) implementation. It is the responsibility of this class to continue the
execution of the process. Attaching the behaviour to the transition is definitely not a
good solution as you want the node (or activity) to be the representation of this
particular step in the process, not the transition from a dummy activity to another.
The asynchronous invocation of ESB services is not properly
implemented
-----------------------------------------------------------------------
Key: GPD-298
URL:
https://jira.jboss.org/jira/browse/GPD-298
Project: JBoss jBPM GPD
Issue Type: Bug
Components: jpdl
Affects Versions: jBPM jPDL Designer 3.1.5
Reporter: Jiri Pechanec
Assignee: Koen Aers
The plugin generates node with call to EsbNotifier to implement the async invocation of
ESB service. This is not correct. The EsbNotifier should be used only on transitions.
http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.GA/html-single/Se...
The current use would mean that the service is inovked and the process will not continue
as there will be no way how to signal it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira