Announcing Mule 3.2.0, Milestone 1

motif

The Mule team is very pleased to announce the first milestone release of Mule 3.2.0.  This is the first public glimpse of the changes coming in Mule 3.2, which include:

  • The Mule Event Store, which is a new, powerful, and flexible architecture for allowing you to choose which events need to be persisted, and where to store them.  Once fully fleshed out, this will allow you to persist the state for Mule constructs like the idempotent-filter and the aggregators, as well as your own custom components.  For more details about how to store SEDA queue events in the Event Store, see here.
  • A new router until-successful, which will keep sending a message until the send succeeds, up to a specified number of retries.  For instance:
  • In case of failure, the send will be retried up to five times , 60 seconds apart. Note that an Event Store store called retryStore is created; this will be used to store the event between retries. For more details see here.

  • Continuing enhancement of Mule Flows.  In this milestone, we add SEDA queues, giving flows the same scalability and high performance as services,  and a simple yet powerful syntax for the times when you need to customize them. You can see the details here.
  • Per-application log files.  Each application now gets its own log file and its own log configuration.  This is discussed here and documented here.
  • A new, much simpler way to configure data sources for JDBC.  For instance, what used to require
  • <spring:bean id="dataSource" class="org.enhydra.jdbc.standard.StandardDataSource" destroy-method="shutdown">
        <spring:property name="driverName" value="com.mysql.jdbc.Driver"/>
        <spring:property name="url" value="jdbc:mysql://localhost/mule"/>
        <spring:property name="user" value="mysql"/>
        <spring:property name="password" value="secret"/>
    </spring:bean>
    

    can now be configured as

    This simple configuration is available for such JDBC drivers as Derby, MySQL, Oracle, and PostgreSQL. For more details, see this.

  • Drools support, which allows you to integrate Mule with a powerful, best-of-breed open source business rules engine.  For more details, see parts 1 and 2 of our series on business rules engines.
  • A new module system that lets you package each Mule application with the plugins (e.g. cloud connectors) it uses and define where to find the classes for each application and plugin and how to resolve any conflicts.   All the details here.
  • Fixes for over 60 important bugs including several patches submitted by you, the community

As always, we appreciate your feedback, bug reports, suggestions and blogs on Mule.  The community’s enthusiasm is a big part of what keeps us going. The milestone can be downloaded here; take it for a spin and let us know what you think.


We'd love to hear your opinion on this post