Bug 778828 (SOA-1276)

Summary: EBWS (ESB Based Web Service) is not documented in programmer's guide
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Aaron Pestel <ammppp>
Component: DocumentationAssignee: Kevin Conner <kevin.conner>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5.0.2   
Target Milestone: ---   
Target Release: 5.1.0 GA   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1276
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-09 09:49:33 UTC Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Aaron Pestel 2009-04-08 00:01:09 UTC 
Date of First Response: 2009-10-27 15:43:03
project_key: SOA

EBWS (ESB Based Web Service) is not documented in programmer's guide:  http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.GA/html-single/Programmers_Guide/index.html#chap-SOA_ESB_Programmers_Guide-Web_Services_Support

There is an example in publish_as_webservice quickstart.
Comment 1 Burr Sutter 2009-10-27 19:43:03 UTC 
Darrin, I think this one is for you, and it is more of a bug than a feature request
Comment 2 Kevin Conner 2009-10-27 19:47:27 UTC 
It seems to already contain the following, although in the contract section where it is defined.

"Exposing an ESB service as a web service
Declaration of the contract schemas will automatically enable the exposure of the ESB service through a web service endpoint, the contract for which can be located through the contract web application. This functionality can modified by specifying the 'webservice' attribute, the values for which are as follows.

    *

      false

      No web service endpoint will be published
    *

      true

      A web service endpoint is published (default) 

The following example illustrates the declaration of a service which wishes to validate the request/response messages but without exposing the service through a web service endpoint.

<service category="ServiceCat" name="ServiceName" description="Test Service">
    <actions mep="RequestResponse" inXsd="/request.xsd" outXsd="/response.xsd"
            webservice="false" validate="true">
        <!-- .... -->
    </actions>			
</service>

The following example illustrates the declaration of a service which wishes to validate the request/response messages and expose the service through a web service endpoint. In addition the service expects the request to be provided in the named body location 'REQUEST' and will return its response in the named body location 'RESPONSE'.

<service category="ServiceCat" name="ServiceName" description="Test Service">
    <actions mep="RequestResponse" inXsd="/request.xsd" outXsd="/response.xsd"
            validate="true" requestLocation="REQUEST" responseLocation="RESPONSE">
        <!-- .... -->
    </actions>			
</service>
"
Comment 3 Anne-Louise Tangring 2010-12-06 18:53:13 UTC 
Kevin, you said this was no longer an issue. Please mark as resolved. Thanks.
Comment 4 Kevin Conner 2010-12-09 09:49:33 UTC 
Already included in documentation