Almost any application you build using Mule will require some kind of data transformation. One thing that I frequently hear come up on the user lists, when I’m talking at JUGs, etc, is how to easily map data between XML formats, Java Beans, and flat files. If you have used Mule at all, you’ll know there are several solutions already for doing this, both as part of Mule and available through a number of great MuleForge projects.
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,
In this episode, MuleSource Sr. Director of Engineering speaks with Edwin Tellman, creator of The Science Service Bus (SSB). As the name implies, the SSB allows programs to send data to each other and serves as a translator service, translating the data from the format preferred by the source application to the format preferred by the destination application. It is inspired by, and is backwards-compatible with the Gaggle program.
We have been running Galaxy successfully on our in-house servers and laptops for demo purposes for some time now and decided that having a running image of Galaxy on Amazon’s EC2 was the next logical step. Galaxy in the cloud gives us the opportunity to expose a running instance to a much wider audience than might otherwise interact directly with the product.
We’re happy to announce the availability of the RESTpack connectors for Mule 2.2, which include support for Jersey, Abdera, and Restlet. In addition to supporting the latest Mule 2.2 codebase, the following improvements have been made:
- JERSEY-8: Filters and security are now correctly applied to endpoints.
- JERSEY-2: Endpoints are now synchronous by default
- Upgraded to the Jersey 1.0.2 release
- RESTLET-9: Restlet Request ChallengeResponse is not properly initialized (Guards now work correctly in Mule)
- The Abdera connector now contains an EntryBuilderTransformer,
We are pleased to announce the General Availability of Mule Enterprise 2.2. This release includes all the great features and bug fixes in the latest Community Release and more. An evaluation of Mule Enterprise 2.2 can be downloaded, or existing customers can access it via the MuleSource Support Portal.
We are pleased to announce that the community release of Mule 2.2.1 is now available for download. This is a maintenance release for Mule 2.2 that includes several bug fixes for passing message properties between CXF endpoints, complex regular expressions in JDBC statements, ordering of events from the <correlation-resequencer-router/>, and more.
Are you currently using Mule or evaluating Mule for use with your WebSphere MQ messaging system? Do you need to utilize WebSphere MQ specific messaging headers, message types, and character code IDs with Mule? Would you like to know how to deploy Mule for maximum reliability when coupled with WebSphere MQ?
Learn from the MuleSource technical team how to integrate Mule with WebSphere MQ using the premium WebSphere MQ transport that is packaged with Mule Enterprise.
On Monday, I spoke to a standing room only crowd at the San Francisco Java Users Group about using the Mule ESB to integrate applications. We talked about:
- What Mule is and what is the difference between integration and SOA
- Why use a Mule for integration
- How Mule helps with integration in the Cloud
- Best practices for planning and implementation
- Test driven development with Mule
Though some think SOA failed and others see it only as a partial success, this has been because of the approach to SOA and not its underlying principles. SOA (or what I’d rather call Service Orientation, but that doesn’t fit our obsession with TLAs) is responsible for beginning a new evolution in the way we build software. This change is as fundamental as the shift to OO programming but essentially a much bigger jump: OO was adopted one developer at a time,