We are pleased to announce the 1.0-M1 release of ServiceMix!

Download Here

Download

Description

servicemix-1.0-M1.zip

Binary Distribution in zip package

servicemix-1.0-M1-src.zip

Source Distribution in zip package

servicemix-1.0-M1.tar.gz

Binary Distribution in gz package

servicemix-1.0-M1-src.tar.gz

Source Distribution in gz package

Changelog

For a more detailed view of new features and bug fixes, see the release notes

Summary

ServiceMix is an open source ESB designed from the ground up on JBI (JSR 208) principles, semantics and APIs. ServiceMix includes a complete JBI container including the Normalised Message Service and Router, the JBI Management MBeans support for JBI deployment units and Ant tasks to install components and manage the container.

In addition ServiceMix contains a suite of JBI components

SOAP Bindings:

  • SAAJ & Apache Axis, WSIF, ActiveSOAP and XFire

Transport components:

  • JMS, HTTP, email, FTP, Jabber, Mule

JBI services:

  • WS-BPEL support via PXE (http://pxe.fivesight.com)
  • transformation via XSLT
  • caching via JCache
  • timing & scheduler services using JCA and Quartz,
  • validation through XSD/RelaxNG
  • scripting via JSR 223 and Groovy

For more detail see the Components list.

ServiceMix has support for straight through processing, SEDA based process flows or fully clustered process flows.

ServiceMix includes a fully integrated JCA container for high performance inbound message consumption (e.g. via JMS) with connection & thread pooling, transaction management, exception and retry handling and support for highly concurrent processing.

ServiceMix is completely integrated into Apache Geronimo, which allows you to deploy JBI components and services directly into Geronimo and ServiceMix will be JBI certified as part of the Geronimo project.

We welcome contributions, please do come and join our team.

For more information see the getting started guide.

Detail

type key summary assignee reporter priority status resolution created updated due

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  • No labels