Section | ||
---|---|---|
|
...
|
...
ServiceMix is lightweight and easily embeddable, has integrated Spring support and can be ran at the edge of the network (inside a client or server), as a standalone ESB provider or as a service within another ESB. You can use ServiceMix in Java SE or a Java EE application server.
The aim of JBI is to allow integration components and services to be integrate in a vendor independent way, allowing users and vendors to plug and play.
Here's an overview of a typical JBI enabled SOA from Sun
Components
ServiceMix currently has JBI components for:
- ActiveSOAP
- Cache for caching service invocations using a Map cache or a JCache provider
- Groovy
- HTTP
- Jabber to provide bindings to Jabber network via the XMPP protocol
- JMS via the Java Messaging Service
- JCA allows the Java Connector Architecture to be used for efficient thread pooling, transaction handling and consumption on JMS or other Resource Adapters
- JSR223
- Mule
- Quartz
- Reflection to allow POJOs to be deployed in ServiceMix
- SAAJ for Soap With Attachments and Apache Axis support
- Validation for schema validation of documents using JAXP 1.3 and XMLSchema or RelaxNG
- XFire for clean integration with POJOs via the XFire SOAP stack
- XSQL for working with SQL and XML via Oracle's XSQL library
- WSIF
ServiceMix also provides a simple to use Client API for working with JBI components and services.
In addition ServiceMix provides an implementation of WS Notification.
Architecture
The following diagram shows the architecture we're aiming for for 1.0.
|
Tip: We're currently working on a new documentation set for ServiceMix. Get a sneak preview here and stay tuned for updates!
News
Blog Posts | ||||
---|---|---|---|---|
|
...