Hide Forgot
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.
Darrin, I think this one is for you, and it is more of a bug than a feature request
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> "
Kevin, you said this was no longer an issue. Please mark as resolved. Thanks.
Already included in documentation