Cargo is a library providing a thin abstraction layer above containers life cycle and applications deployment. Think about integration testing Swiss army knife. It can be used from ant, maven or as a Java library to manipulate most available containers.
Starting today cargo has an open-source Mule implementation.
In order to make sure that the migration path is straightforward and well-documented, I just finished migrating the SFTP MuleForge project from Mule ESB 2.2.1 to 3.0. It was extremely helpful to have a good set of unit tests in the SFTP transport code. That makes it easier to tell if your project still has all of the necessary functionality after the migration. If you are interested in migrating your own MuleForge project,
Just as we’re always driving Mule ESB to make it easier to use, we’re also always taking user feedback and revving the Mule Community website to make it easier to find what you need, when you need it. The Mule Community website has a new look, so check it out!
The Galaxy team is happy to announce the availability of the 1.5.2 release. This release provides several improvements:
- Support for Mule 2.2
- Policy enforcement now occurs correctly when metadata changes and lifecycle transitions occur
- Policies can now be applied to Entries
- Metadata properties can now be deleted via the API
- Performance improvements
- Dependency/link searches now work correctly
- The default version of entries can now be set without an error being thrown
- The Galaxy Enterprise database configuration tool now works correctly on Windows
For more information,
Hot on the heals of the Mule 2.1.2 release, we’ve pushed out a new release of Galaxy as well. This release contains many improvements:
- A new custom policy example
- A new AtomPub API usage example
- Fixed LDAP Integration
- Many bug fixes!
For more information, cruise over the release notes and download page. As always, we’re anxious to hear your feedback via the mailing list or comments below.
Galaxy includes many standard events you can use right out of the box, such as ENTRY_CREATED and LIFECYCLE_TRANSITION. (For the full list, click here). Using the Event API, you can also create your own events and create scripts that listen for them.
You may have noticed a lot of changes to the MuleSource documentation wiki lately. With the help of all of our great developers, I’ve been slowly updating the pages, validating content, updating outdated information, and restructuring. We’ve also added a lot of new content to the Getting Started guide and set up navigation so that it flows like a book, making it easier for new users to get up and running.