Web service proxies

Another useful capability of JBoss ESB is to act as a proxy for existing web services. There are a number of reasons why this could be desirable, including controlling access to the service, modifying request and/or response invocations, redirecting requests to different versions of the web service, exposing a subset of the functionality and more. JBoss ESB forms a bridge between the client and the web service, reducing the coupling between the two endpoints. This reduced coupling increases the flexibility inherent in the system, allowing it to adapt to changes as and when they arise.

SOAPProxy

There are a number of parameters that can be specified with the SOAPProxy action:

  • wsdl: a mandatory URL representing the WSDL for the original service
  • wsdlTransform: an optional transformation resource that can be applied to the original WSDL before publishing
  • wsdlCharset: an optional parameter specifying the character set of the original WSDL, if necessary

A basic example configuration would look like the following:

<action class="org.jboss.soa.esb.actions.soap.proxy.SOAPProxy"
        name="proxy-action">
  <property name="wsdl"
            value="http://localhost:8080/BookService?wsdl"/>
</action>
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset