2. Mule is designed to facilitate the use of Web
services in the following ways:
Web services can be hosted or consumed
Transport decoupled from protocol, that is, you
can send /receive over JMS, email, etc.
JAX-WS or Simple services
Web services can be proxied or modified
without much code
Prudhvi
3. Proxying Web Services
Mule can act as a Web Service gateway/proxy.
Gateways can perform several useful functions:
Routing to the appropriate backend service
(whether remote or local)
Message transformations, such as converting from
old versions of the message format
Protocol bridging, such as HTTP to JMS
Validation
Security enforcement
WS-Policy enforcement
Prudhvi
4. Mule provides several utilities that help you do
this:
Protocol bridging - allows you to forward requests from
one endpoint to another. This is generally the best option
for proxying Web Services.
WSProxyService - allows you to service WSDLs locally
while proxying remote web services.
Proxying Web Services - perform WS-Security or WS-
Policy actions, route based on information such as the
operation or SOAP Action, and easily work with just
the payload by taking advantage of CXF's web
service capabilities
Prudhvi
5. Protocol Bridging
The simplest type of Web Service proxy just
involves forwarding a request from one endpoint
to another via service . You can forward the
Bridging data streams directly, or you can process
and transform the XML. If you are doing content-
based routing, this is often the best option, as it
will add less overhead than a full CXF proxy
(which is only needed in certain cases).
Prudhvi
6. WSProxyService
The WSProxyService allows you to serve WSDLs
locally while proxying remote web services. This is
handy when you have an alternate WSDL you want
to service, or if you don't want WSDL requests to
be routed with all the other SOAP message
requests. Any request that comes in with a
"?wsdl" attached to the HTTP URL will be
redirected, and the specified WSDL will be served
instead.
Prudhvi
