Components list

ServiceMix currently has the following JBI components:

Standard JBI components

The following components ships with ServiceMix distribution:

• 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

External standard JBI components

• BPEL support for WS-BPEL via ODE
• BpmScript is a Business Process Engine written using Rhino continuations
• JAFS is an FTP server embedded in a JBI component
• JBI4Corba a JBI component for working with CORBA services
• JBI4Cics a JBI component for working with CICS services
• JBI4Ejb a JBI component for working for existing EJBs
• and many more...

Lightweight components

ServiceMix also provides some lightweight components, but theses are rather deprecated and the standard components above should be used instead.