You can extract the request, response and fault schemas from your existing WSDL and then can host them as a WebService in ESB. Checkout the publish_as_webservice quickstart. Of course you will have to write the Action classes to handle these SOAP messages.
Are you sure you don't need to use the ESB only as a proxy for webservices? This is a common usage of ESB with alredy defined webservices.
There are many ESB out of the box actions for webservices, have a look at them (SoapClient,SoapProxy,SoapProcessor)
Right... maybe provide a few more details. You may want:
- What Magesh is referring to if you want to manually process the SOAP payload in an ESB action, or
- The SOAPProxy if you are proxying a WS call through the ESB to a target Webservice endpoint, or
- To implement a JSR181 Webservice (bundled into your ESB for deployment) that uses the ServiceInvoker to invoke your WS enpoint. This approach gives you full control over jax-ws handlers etc, if that's what you need.
Prob more options, but depends on what you're doing.