THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
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 (deprecated)
- 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-mail Email Binding Component
- servicemix-osworkflow OSWorkflow Service Engine
- servicemix-quartz
- servicemix-saxon
- servicemix-script uses Spring Dynamic Language Support
- servicemix-scripting JSR-223 Scripting Engine
- servicemix-smpp SMPP (SMS) Binding Component
- servicemix-snmp SNMP Binding Component
- servicemix-truezip
- servicemix-validation a xml validation engnine
- servicemix-vfs a vfs binding component based on Apache Commons-VFS
- servicemix-wsn2005 is an implementation of WS-Notification
- servicemix-xmpp is an XMPP (Jabber) Binding Component
Components Roadmap
The following list shows the future components that will be included in ServiceMix distribution :
Component |
Type |
Description |
Status |
Jira |
Resource |
|---|---|---|---|---|---|
servicemix-ldap |
BC |
Poll and send data with a LDAP directory server. |
Proto |
|
|
servicemix-exec |
SE |
Executes system command (shell or bat script) and return the standard output into a normalized message. |
Proto |
|
|
servicemix-jcom |
BC |
Uses the Java Communication API (http://java.sun.com/products/javacomm/) |
TODO |
|
|
servicemix-jdbc |
BC |
Uses JDBC connectivity to poll and send data within a database |
TODO |
|
|
servicemix-rmi |
BC |
Uses to get and send marshaled object using RMI-IIOP ORB |
TODO |
|
|
servicemix-talend |
BC |
Uses to get/put data coming from/to Talend ETL |
TODO |
|
|
servicemix-asterisk |
BC |
Uses to get/put data coming from/to Asterisk VOIP server |
TODO |
|
|
servicemix-sip |
BC |
Uses SIP protocol to get/put data |
TODO |
|
|
servicemix-rssatom |
BC |
Uses to get/put data coming from/to RSS/Atom stream |
TODO |
|
|
servicemix-dcom |
BC |
Uses to get/put data using Microsoft's DCOM protocol |
TODO |
|
|
servicemix-sap |
BC |
Interface with SAP |
TODO |
|
|
Third Party Standard JBI Components
These components are a wonderful benefit of JBI that is a direct result of the JBI spec. Because the JBI spec is open, many vendors provide JBI compliant components that can be deployed in ServiceMix.
Apache ODE
Apache Ode is a BPEL engine which provides a JBI compliant component that can be easily deployed into ServiceMix.
Sun OpenESB JBI Components
The Sun OpenESB is based on JBI and provides many JBI compliant components that can also be used in ServiceMix.
ObjectWeb Petals Components
The Petals ESB is also based on JBI and provides JBI compliant components as well.
Various Highly Useful JBI Components
- Support for WS-BPEL is provided via Apache 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
Lightweight components
ServiceMix also provides some lightweight components, but theses are rather deprecated and the standard JBI components above should be used instead.