Bug 1123686

Summary: Lack details, use cases and examples for interface type ESB
Product: [JBoss] JBoss Fuse Service Works 6 Reporter: rmarins <rmarins>
Component: DocumentationAssignee: soa-docs <soa-docs>
Status: CLOSED DUPLICATE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0.0 GACC: belong, nobody, soa-p-jira
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-29 03:02:47 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:
Embargoed:

Description rmarins@redhat.com 2014-07-27 23:43:40 UTC
The service contract type ESB in Switchyard is not intuitive and the current documentation doesn't give further explanation about it. It's briefly mentioned on Section 3.4 of Development_Guide_Volume_1_SwitchYard (manual identifier) and that's all.

Found this community discussion useful: https://community.jboss.org/thread/235374

However, it's not complete. Users must have wider understanding of it and how to put in to work.

Comment 1 belong 2014-07-29 03:02:47 UTC
Thank you for your feedback.

This is already a known issue and has been marked as high priority.

Closing as a duplicate.

*** This bug has been marked as a duplicate of bug 1121477 ***