Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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
  • WS-Addressing support
  • WSDL based and XBean based deployments
  • Support for all MEPs as consumers or providers

...

Info
titleConfiguration
borderStylesolidbgColor='lighblue'

Name

Type

Description

Default

streamingEnabled

boolean

send client side requests using HTTP streaming

false

jettyConnectorClassName

String

Jetty connector class name

org.mortbay.nio.SelectChannelConnector

jettyThreadPoolSize

int

thread pool size for server side requests

255

maxConnectionsPerHost

int

max number of simultaneous connections to a given host

32

maxTotalConnections

int

max number of total simulatenous connections

256

XBean deployment

You can deploy Service Units containing a file named xbean.xml for activating
consumer and provider endpoints.

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.

Any numbers of endpoints can be specified in the xbean.xml file.

Consumer endpoint

Wiki Markup
{snippet:id=consumer|lang=java|url=http://svn.apache.org/repos/asf/incubator/servicemix/trunk/servicemix-http/src/test/resources/xbean/xbean.xml}

Provider endpoint

Wiki Markup
{snippet:id=provider|lang=java|url=http://svn.apache.org/repos/asf/incubator/servicemix/trunk/servicemix-http/src/test/resources/xbean/xbean.xml}

Lightweight mode

Wiki Markup
{snippet:id=lightweight|lang=java|url=http://svn.apache.org/repos/asf/incubator/servicemix/trunk/servicemix-http/src/test/resources/org/apache/servicemix/http/addressing.xml}