...
This xml file should respect the given syntax, though this is a spring based xml configuration file from where all beans of class HttpEndpoint are retrieved.
See a full example here. Note that you have to define the http namespace with
Code Block | ||||
---|---|---|---|---|
| ||||
<beans xmlns:http="http://servicemix.apache.org/http/1.0"> ... </beans> |
Any numbers of endpoints can be specified in the xbean.xml file.
...
Info | ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||
|
WSDL Deployment
In addition to xbean based deployment, the component accepts WSDL-based deployment.
The service unit may contain any number of WSDL files, each one being parsed and activating the specified endpoints.
To retrieve the necessary informations from the wsdl, the component can recognize a jbi extension, in addition to the standard http and soap bindings, which specified the role of the component and the default MEP to use for JBI exchanges.
Here is an example of a WSDL:
Wiki Markup |
---|
{snippet:id=wsdl|lang=xml|url=http://svn.apache.org/repos/asf/incubator/servicemix/trunk/servicemix-http/src/test/resources/consumer/http.wsdl} |
Lightweight mode
The servicemix-http component can also be configured in a spring/xbean configuration file, for use in an embedded ServiceMix.
Here is an example of such a configuration:
Wiki Markup |
---|
{snippet:id=lightweight|lang=xml|url=http://svn.apache.org/repos/asf/incubator/servicemix/trunk/servicemix-http/src/test/resources/org/apache/servicemix/http/addressing.xml} |
...