Home - Apache ServiceMix - Apache Software Foundation
This project has retired. For details please refer to its
Attic
page.
DUE TO SPAM, SIGN-UP IS DISABLED. Goto
Selfserve wiki signup
and request an account.
Apache ServiceMix
Pages
Blog
Child pages
Pages
Board reports
Community
Developers
Documentation
Downloads
How to Evaluate an ESB
JavaOne Meetup 2008
Overview
Release notes
ServiceMix 3 Project Refactoring
ServiceMix 3 Website Refactoring
ServiceMix 4.3.0
ServiceMix 4.4.0
ServiceMix Releases Template
User's Guide
Users space
13 more child pages
Browse pages
tachments (6)
Page History
Resolved comments
Page Information
View in Hierarchy
View Source
Export to PDF
Export to Word
Copy Page Tree
Jira links
Created by
James Strachan
, last modified by
Gert Vanthienen
on
Mar 04, 2011
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
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.
Permalink
Jul 19, 2005
James Strachan
Agreed - we've just about got the nightly build working - at least the snapshot release should work now
Permalink
Jul 22, 2005
Unknown User (monzdrpower)
Hi
My question about JNDI init. I have local jndi.xml like this
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?
Permalink
Sep 07, 2005
Unknown User (monzdrpower)
No, local "java.naming.provider.url =
file://jndi.xml
" causes "UnknownHost jndi.xml" exception at SM startup
Permalink
Sep 07, 2005
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.
Permalink
Sep 10, 2005
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?
Permalink
Jan 31, 2006
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
Permalink
Jan 31, 2006
Overview
Content Tools
Atlassian Confluence Open Source Project License
granted to Apache Software Foundation.
Evaluate Confluence today
Atlassian Confluence
8.5.31
Printed by Atlassian Confluence 8.5.31
Report a bug
Atlassian News
Atlassian
{"serverDuration": 279, "requestCorrelationId": "46c3b4b4cd82e469"}
US