This release introduces two transformers, mongodb:db-file-to-byte-array and mongodb:db-file-to-input-stream, that simplify getting at the contents of GridFSDBFiles.

The release notes can be found at: http://www.mulesoft.org/documentation/display/MONGODB/Home

The Smooks for Mule team is pleased to announce the availability of the Smooks for Mule 1.2 release. Smooks for Mule enables Message Transformation and Routing using the Smooks. The module is now compatible with the Mule 2.2.x releases. However the Mule 2.0.x and 2.1.x releases are not supported any more. The Smooks library is upgraded to version 1.3.1.

The release notes can be found at: http://www.mulesoft.org/display/SMOOKS/Release+notes+1.2

We are happy to announce a release candidate #2 of the Mule SFTP Transport 2.2.1 which is targeted for Mule 2.2.1.

Release notes can be found at http://www.mulesoft.org/jira/secure/ReleaseNote.jspa?projectId=10064&styleName=Html&version=10782

I’m happy to to announce that mule 2.2.x can now utilize Tibco’s Rendezvous messaging system. This release maintains all of the features of the 1.4.1 release such as certified messaging, distributed queues, and runtime defined endpoints.

Check out the user guide http://www.mulesoft.org/display/TIBCORV/User+Guide+2.2.x which details how to configure the transport.

We are happy to announce a release candidate of the Mule SFTP Transport 2.2.1 which is targeted for Mule 2.2.1. New features:

• Added support for connection pooling (SFTP-6)
• Added sftp specific server notifications (SFTP-11)
• Added support for identity files (authentication using keys, not password)
• Added fileAge support (that is, a miniumum age (ms) for a file to be processed
• Added archive support (stores a copy of the file on the Mule server)
• Added duplicate handling support (throwException, addSeqNo, overwrite[not yet implemented])
• Added temp directory support – The file is first uploaded to a temporary directory. When the file is fully uploaded the file is moved to its final destination. The tempDir will be created as a sub directory to the endpoint. Other significant changes:
• Updated the path-handling to be spec-compliant (SFTP-13). Note, this probably mean that current users must update their paths.
• Fixed so that the file in the inbound directory is not deleted if some error occurs when writing to the outbound directory
• Improved error information regarding connection-related errors.
• Upgraded jsch from 0.1.29 to 0.1.42
• Bug fix: SFTP transport doesn’t work with the Quartz transport (SFTP-9)
• And other small fixes…’ Project URL: http://www.mulesoft.org/display/SFTP/Home

Reconnect Bug fixed in LDAP Transport 2.2.1.1. LDAP Transport for Mule 1.4 and 2.0 reaches end of life and are no longer maintained.

This new release is targeted at Mule 2.2.1.

New features:
– Generated COBOL<→Java and COBOL<→XML Transformers are usable independently from Transports.
– Support for WebSphere MQ and the IBM CICS MQ Bridge (No need to install LegStar on the mainframe with this deployment type).
– Configuration uses the Mule configuration framework. You can configure your mainframe access directly within Mule XML files.

We are proud to announce the next stable release of the Mule LDAP Transport 2.2.1.0 which is intended for Mule 2.2.1.

New Features:
- Additional Tranformer: LDAPSearchResultsToJavaBean (contributed by Tomas Blohm)

The LDAP Transport provides support for connecting directory services via ldap/ldaps (also via SASL).
Its fully LDAP V3 compliant and supports DSML and LDIF.

I am happy to announce the release of version 2.2.0 of the JCR Transport, which will bring intense content happiness to your favorite latest Mule.

Release Notes: http://www.mulesource.org/jira/secure/ReleaseNote.jspa?projectId=10121&styleName=Html&version=10629

Project URL: http://www.mulesource.org/display/JCR/Home

We are proud to announce the next stable release of the Mule LDAP Transport 2.2.0.0 which is intended for Mule 2.2.0. The LDAP Transport provides support for connecting directory services via ldap/ldaps (also via SASL). Its fully LDAP V3 compliant and supports DSML and LDIF.