Apache ServiceMix is a flexible, open-source integration container that unifies the features and functionality of Apache ActiveMQ, Camel, CXF, ODE, Karaf into a powerful runtime platform you can use to build your own integrations solutions. It provides a complete, enterprise ready ESB exclusively powered by OSGi.

It is being released under Apache License.

The main features are:

  • reliable messaging with Apache ActiveMQ
  • messaging, routing and Enterprise Integration Patterns with Apache Camel
  • WS-* and RESTful web services with Apache CXF
  • loosely coupled integration between all the other components with Apache ServiceMix NMR including rich Event, Messaging and Audit API
  • complete WS-BPEL engine with Apache ODE
  • OSGi-based server runtime powered by Apache Karaf
Download ServiceMix 4.3.0

Tip: We're currently working on a new documentation set for ServiceMix. Get a sneak preview here and stay tuned for updates!

News

ServiceMix 4.3.0 Released
Jean-Baptiste Onofré posted on Mar 04, 2011

The ServiceMix team is pleased to announce the availability of ServiceMix 4.3.0.
This is a major release of ServiceMix and contains many bug fixes as well as new features.
For more information, please see the release notes

ServiceMix 4.2.0 Released
Chris Custine posted on Apr 27, 2010

The ServiceMix team is pleased to announce the availability of ServiceMix 4.2.0.
This is a major release of the OSGi based ServiceMix 4.2.0 and contains many bug fixes as well as new features.
For more information, please see the release notes

ServiceMix 3.3.2 released
Jean-Baptiste Onofré posted on Apr 20, 2010

The ServiceMix team is pleased to announce the availability of ServiceMix 3.3.2.
This releases fixes a number of bugs and ships with the latest 2010.01 version of all the JBI components.
For more informations, please see the release notes

ServiceMix 3.3.1 released
Gert Vanthienen posted on Jun 23, 2009

The ServiceMix team is pleased to announce the availability of ServiceMix 3.3.1.
This releases fixes a number of bugs and ships with the latest 2009.01 version of all the JBI components.
For more informations, please see the release notes

ServiceMix 3.2.3 released
Freeman Yue Fang posted on Oct 29, 2008

The ServiceMix team is pleased to announce the availability of ServiceMix 3.2.3.
This release includes a number of bug fixes and improvements.
For more informations, please see the releasenotes

More News

  • No labels

7 Comments

  1. Unknown User (marco_antonioni@it.ibm.com)

    A nightly build distribution may be a nice to have, i'm trying to use the snapshot jar but it is very far from the online doc, the email componenent is not present.
    Anyway this is a very interesting initiative.

  2. James Strachan

    Agreed - we've just about got the nightly build working - at least the snapshot release should work now

  3. Unknown User (monzdrpower)

    Hi
    My question about JNDI init. I have local jndi.xml like this

    <beans>
    <bean id="jndi" class="org.servicemix.jbi.jndi.DefaultContext" singleton="true">
    <property name="entries">
    <map>
    <entry key="jdbc/nemo">
    <bean class="org.hsqldb.jdbc.jdbcDataSource">
    <property name="database" value="jdbc:hsqldb:mem:nemodb"/>
    <property name="user" value = "sa"/>
    <property name="password" value = ""/>
    </bean>
    </entry>

    <entry key="javax.transaction.TransactionManager">
    <bean class="org.jencks.factory.TransactionManagerFactoryBean"/>
    </entry>
    </map>
    </property>
    </bean>
    </beans>

    and jndi.properties like this

    java.naming.factory.initial = org.servicemix.jbi.jndi.SpringInitialContextFactory
    java.naming.provider.url = file://jndi.xml

    when SM startup, it reads this files with no comments/errors
    but when hibernate query execute - SM reads its own $SM_HOME/conf/jndi.xml (I suppose) with exception - "datasource jdbc/nemo not found".

    How can I REALLY init SM with local jndi.xml?

  4. Unknown User (monzdrpower)

    No, local "java.naming.provider.url = file://jndi.xml" causes "UnknownHost jndi.xml" exception at SM startup

  5. Unknown User (vadim.ivanov)

    Note: "java.naming.provider.url = file:./jndi.xml" variant does not cause exception, but "servicemix_home/conf/jndi.xml" file is still used only.

  6. Unknown User (zhuodan)

    I just found SOAP binding component like SaajBinding component will set NMS content to be whole SOAPPart, in such a way it could make other Component (SE) SOAP-aware. Is binding component should remove the protocol specific structure or should still keep it within NMS content. what is the best strategy should take for SOAP binding component?

      

  7. Guillaume Nodet

    You are right and this is no longer the case in servicemix-3.0-SNAPSHOT.  Note that the best way to send such comments is always the mailing list (smile)