| h1. servicemix-http |
| |
| h2. Overview |
| ServiceMix ships with a JBI compliant HTTP/SOAP binding component named servicemix-http. |
| |
| Here are the main features: |
| * JBI compliant Binding Component |
| * Usable in a lightweight mode in servicemix.xml configuration files |
| * Integrated HTTP server based on Jetty 6 |
| * HTTP Client using Jakarta Commons HTTP Client |
| * Highly performant and scalable using Jetty 6 continuations |
| * SOAP 1.1 and 1.2 support |
| * MIME attachments |
| * WS-Addressing support |
| * WSDL based and XBean based deployments |
| * Support for all MEPs as consumers or providers |
| * SSL support |
| * WS-Security support |
| |
| |
| h3. Namespace and xbean.xml |
| The namespace URI for the servicemix-bean JBI component is {{http://servicemix.apache.org/http/1.0}}. This is an example of <filename>xbean.xml</filename> file with a namespace definition with prefix {{bean}}. |
| {code} |
| <beans xmlns:http="http://servicemix.apache.org/http/1.0"> |
| |
| <!-- add http:consumer, http:soap-consumer |
| http:provider and http soap:provider definitions here --> |
| |
| </beans> |
| {code} |
| |
| h3. Endpoint types |
| The servicemix-http component defines four endpoint type: |
| - {{http:consumer}} :: This endpoint allows you to expose a service in the ESB to the outside world over HTTP. Whenever it receives an HTTP request, it will interact with the configured services on the ESB to provide the HTTP response. |
| - {{http:soap-consumer}} :: Similar to {{http:consumer}}, but specifically geared towards handing SOAP requests and responses |
| - {{http:provider}} :: This endpoint allows you to access remote services from within the ESB. It will perform an external HTTP request whenever it receives a JBI MessageExchange |
| - {{http:soap-provider}} :: Similar to {{http:provider}}, but specifically geared towards performing SOAP requests |
| |
| It also provides one additional legacy endpoints, which are still available to ease migration from ServiceMix 3: |
| - {{http:endpoint}} :: (Deprecated) Legacy endpoint, capable to acting as a consumer or provider based on the configuration |
| |
