-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Blocker
-
Resolution: Done
-
Affects Version/s: 5.0.0 GA
-
Fix Version/s: 5.1.0 GA
-
Component/s: Documentation
-
Labels:
-
Affects:Documentation (Ref Guide, User Guide, etc.)
-
Estimated Difficulty:Low
-
Release Notes Text: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.
-
Release Notes Docs Status:Documented as Resolved Issue
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.
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?
- is blocked by
-
SOA-2183 QE Review - Programmers' Guide
-
- Closed
-
