Bug 778692 (SOA-1159)

Summary:	The asynchronous invocation of ESB services is not properly implemented
Product:	[JBoss] JBoss Enterprise SOA Platform 4	Reporter:	Jiri Pechanec <jpechane>
Component:	Tooling	Assignee:	Mark Little <mark.little>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	4.3 CP01	CC:	koen.aers
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-1159
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	778693 (view as bug list)		Environment:
Last Closed:	2009-12-15 09:18:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jiri Pechanec 2009-02-04 12:57:58 UTC

Date of First Response: 2009-02-04 09:14:33
project_key: SOA

See GPD-298

Comment 1 Jiri Pechanec 2009-02-04 12:58:14 UTC

Link: Added: This issue depends GPD-298

Comment 2 Koen Aers 2009-02-04 14:14:33 UTC

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.

Comment 3 Kevin Conner 2009-02-04 14:18:44 UTC

Sorry Koen but can you elaborate on this?

This class was always intended to be used within a transaction/event and not an action on the main node.  The one which *is* part of the main node, and does indeed stop processing while waiting for a response, is the EsbActionHandler.

Comment 4 Kevin Conner 2009-02-04 14:19:25 UTC

Sorry, last should read *transition* and not transaction.

Comment 5 Jiri Pechanec 2009-02-04 14:24:52 UTC

Link: Added: This issue related SOA-1162

Comment 6 Koen Aers 2009-02-04 14:45:23 UTC

So the EsbActionHandler acts as a wait state? It is possible to implement action handlers for nodes that continue the execution themselves (so that the nodes don't act as wait states. And then it is possible to add support for such a node in the GPD. But it is not possible (at the moment) to plug in support for the mere action handler as a predefined action.

Comment 7 Kevin Conner 2009-02-04 14:49:54 UTC

EsbActionHandler will force the token processing to stop at that point, until an asynchronous event.  Once this reply has been received (or a timeout occurs) the token can then proceed.

We handle the resumption of the token processing for EsbActionHandler once an ESB response has been received.

Comment 8 Mark Little 2009-05-26 08:57:03 UTC

From Koen ... "... this has been released with the JBoss Tools 3.0 and JBDS 2.0 releases."

Comment 9 Jiri Pechanec 2009-12-15 09:18:57 UTC

Verified in ER5