{scrollbar}

Components

ServiceMix distribution comes with several ready to use standard JBI components:

• servicemix-bean is a JBI component for mapping beans (POJOs) to JBI message exchanges for easy procssing of JBI message exchanges. Note that if you want to support SOAP, type safe business interfaces or JAX-WS / JSR 181 then you should use servicemix-jsr181
• servicemix-bpe
• servicemix-camel
• servicemix-cxf-bc
• servicemix-cxf-se
• servicemix-drools
• servicemix-eip contains several routing patterns based on the great EIP book
• servicemix-file is a file system Binding Component
• servicemix-ftp is an FTP Binding Component
• servicemix-http is an HTTP/SOAP Binding Component
• servicemix-jms is a JMS Binding Component
• servicemix-jsr181 Service Engine can expose annotated POJOs as services
• servicemix-lwcontainer Service Engine can deploy lightweight components
• servicemix-quartz
• servicemix-saxon
• servicemix-script
• servicemix-truezip
• servicemix-wsn2005 is an implementation of WS-Notification
• servicemix-xmpp is an XMPP (Jabber) Binding Component

Have a look at the Component Matrix for a comprehensive, detailed list of components and their properties.

General concepts

All components accepts a xbean.xml configuration file as the main artifact inside a Service Unit. This file is a spring configuration file.

Spring

XBean

Classpath

Properties

{scrollbar}