Artifacts using servicemix-core version 3.2.2

Common classes used by Apache ServiceMix, Components and utilities.

JBI compliant HTTP/SOAP binding component.

ServiceMix :: Components

The ServiceMix EIP component is a routing container where different routing patterns can be deployed as service unit.

JBI compliant JMS binding component for reading and writing JMS messages using queues and topics.

The servicemix-camel component provides support for using Apache Camel to provide a full set of Enterprise Integration Patterns and flexible routing and transformation in both Java code or Spring XML to route services on the Normalized Message Router.

ServiceMix JSR(181 component is a JBI Service Engine exposing (annotated) POJO as services on the JBI Bus. It uses xfire internally to perform service invocations and xml marshaling.

ServiceMix CXF SE component is a JBI Service Engine exposing (annotated) POJO as services on the JBI Bus. It uses Apache CXF internally to perform service invocations and xml marshaling.

JBI compliant HTTP/SOAP or JMS/SOAP binding component which use Apache CXF internally

The ServiceMix Bean component provides integration with beans (POJOs) with the JBI bus to make it easy to use POJOs to process JBI message exchanges. Like in an Message Driven Bean in J2EE a POJO will receive a message from the NMR and process it in any way it likes. Unlike in a JMS component where the coding is already done the Bean component gives the developer the freedom to create any type of message handling but it must be hand coded all the way.