Overview

Search

Documentation

Community

Developers

Components

Related Projects

This page is a preview of the release page which will be announced and made official once the release has been approved.

Download Here

Linux/Mac OS X/Unix Downloads

Windows Downloads

Release notes

  • Bug
    • SM-387 - JBI Spec - Resource Loading Styles not correctly implemented
    • SM-482 - Missing jars in the BPE component
    • SM-570 - HTTP connector can blow up while trying to report a problem
    • SM-583 - Jetty context Path verification
    • SM-589 - The SourceTransformer should not log a warning when calling toResult with a null Source
    • SM-592 - notifier.run() missing from DefaultState
    • SM-593 - Jetty jars missing when running servicemix-web example
    • SM-597 - Drools xpath expression does not use the namespaces defined
    • SM-598 - MTOM attachments are not output by the jsr181 component
    • SM-599 - bridge sample client.html providing no status info
    • SM-603 - NullPointerException at org.apache.servicemix.jms.standard.StandardConsumerProcessor.doStart(StandardConsumerProcessor.java:51)
    • SM-604 - Allow servicemix-http managed mode to dynamically determine the server, port, and context path it is running on when generating jsr181 WSDLs
    • SM-608 - Maven based examples should include the needed repositories
    • SM-610 - The ServiceAssembly mbean should return the names of the ServiceUnits
    • SM-622 - JCAFlow with Howl Log throws STATUS_NO_TRANSACTION exception
    • SM-674 - jbi:installComponent (and others) fails authentication against default SM container
    • SM-676 - In the instance2 of the ws-notification example, the org.apache.servicemix.tck.ReceiverComponent should be removed
    • SM-677 - FTP connection not recovered after ftp server failure/recovery
    • SM-678 - Jsr181Component not using SU classloader to load service interface
    • SM-691 - Client.html pages do not work in IE
    • SM-697 - Using XSLT servicemix component causes a "java.io.IOException: Too many open files"
    • SM-700 - ClientFactory should log problems at warning level as they are not critical
    • SM-707 - Subscription Manager and Flow MBeans do not get unregistered.
    • SM-722 - ExtendedXMLStreamReader strips whitespaces, which breaks servicemix-http when a SOAP invocation contains whitespace nodes
    • SM-723 - ServiceMixClientFacade should not call "done" method
    • SM-727 - Schema Import problem in a WSDL which doesn't let the service to be doployed on Servicemix
  • Improvement
    • SM-565 - Enhance the JSR181 Proxy so that it can proxy non WSDL publishing components
    • SM-578 - HttpComponent can not be deployed as managed!
    • SM-581 - Use WSDL of servicemix-http endpoint if none is supplied by the target ServiceEndpoint
    • SM-586 - Upgrade loan-broker example to lingo 1.1 and use different queues to avoid recieving messages from previous client runs
    • SM-612 - servicemix-service-engine could set the scope of servicemix-core to provided
    • SM-701 - Standardized the return of exceptions from the AdminCommandsService, also extended the ANT tasks to provide a deferExceptions settings which if set to true allows you to use the same semantics as the deploy/install directories.
    • SM-702 - Components instantiated multiple times
    • SM-709 - Upgrade to xbean 2.7 and Spring 2.0
    • SM-710 - Upgrade to jetty 6.0.1
    • SM-711 - Upgrade to woodstox 3.0.2
    • SM-712 - Upgrade to xfire 1.2.2
    • SM-715 - Document usage of jsr181:endpoint style parameter
  • New Feature
    • SM-605 - Ability to configure jbi:projectDeploy goal to exclude updating dependencies
    • SM-616 - Archetypes for the servicemix-saxon service engine
    • SM-705 - Static Parameter map injected into XsltComponent
  • Task
    • SM-671 - Use RI implementations for activation and javamail instead of geronimo ones

SVN Tag Checkout

svn co http://svn.apache.org/repos/asf/incubator/servicemix/tags/servicemix-3.0.1/

Changelog

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