Bug 779671 (SOA-2036)

Summary: Error in SOA-P 5 Programmer's Guide - All gateways utilise the ServiceInvoker
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Stelios Koussouris <skoussou>
Component: DocumentationAssignee: David Le Sage <dlesage>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: urgent Docs Contact:
Priority: urgent    
Version: 5.0.0 GACC: erics
Target Milestone: ---   
Target Release: 5.1.0 GA   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-2036
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-23 01:08:09 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:
Bug Depends On: 779822    
Bug Blocks:    

Description Stelios Koussouris 2010-04-13 08:31:53 UTC
Affects: Documentation (Ref Guide, User Guide, etc.)
Complexity: Low
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&tid=750143&gid=1354
project_key: SOA

A very keen EAP customer (Globalcollect) has been digging into our JBoss SOA-P 5 and during an extensive workshop I gave yesterday he asked about the
following mentioned in our documentation.

http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/5.0.0/html/Programmers_Guide/chap-SOA_ESB_Programmers_Guide-Advanced_Topics.html

In section 7.1.1 there is a note:

"Because the ServiceInvoker hides much of the fail-over complexity from
users, it, by necessity, only works with native ESB Messages. Additionally, not all gateways have been modified to use the ServiceInvoker. Therefore, incoming ESB-unaware messages for those gateway implementations may  sometimes be unable to take advantage of service fail-over."

He wants a list of the Gateways that have not been using the ServiceInvoker. Anyone have this info handy?
--------------------------
Kevin Conner says:
I've been through the gateways and they all use ServiceInvoker, it looks like the documentation is in error.  Can you raise a SOA jira to have
this corrected?

Comment 1 Anne-Louise Tangring 2010-09-21 20:39:41 UTC
This is a candidate for SOA 5.1.0.

Comment 2 Anne-Louise Tangring 2010-12-06 16:21:06 UTC
Usability and customer sat is important, thus this is made a blocker for SOA 5.1. 


Comment 3 Dana Mison 2010-12-17 02:05:13 UTC
Labels: Added: ESB_Programmers_Guide
Complexity: Added: Low


Comment 4 Len DiMaggio 2010-12-20 02:42:28 UTC
Link: Added: This issue depends SOA-2183


Comment 5 David Le Sage 2010-12-23 01:08:09 UTC
Note removed from product doc.

Comment 7 Dana Mison 2011-01-05 00:12:12 UTC
Writer: Added: Darrin


Comment 8 Dana Mison 2011-02-17 11:21:47 UTC
Release Notes Docs Status: Added: Documented as Resolved Issue
Release Notes Text: Added: The ESB Programmer's Guide incorrectly asserted that not all the gateways used ServiceInvoker.  All the gateways do now use ServiceInvoker and the documentation has been updated to reflect this.