During the QCon conference in San Francisco, I filmed an interview with Ryan Slobojan. Despite being flu-ridden throughout the week, I managed to make it through this conversation without passing out (or worse!). It was an interesting conversation, covering:
- What the Mule ESB and Mule Galaxy are
- Mule ESB Enterprise versus Community
- MuleSource’s monitoring solution
- Cloud-based deployments
- The recession’s effect on open source
Ryan asked some good questions around differentiators and roadmap during the interview, too.
In a previous blog post about the Mule IDE, I described its configuration wizard, which makes it very easy to create a Mule configuration file by selecting the modules and transports you want to include. Today I’d like talk more about what’s going on under the hood and explain how the Mule IDE discovers modules and transports from the Mule distribution directory.
If you’re working with the Mule IDE, the Mule source code is automatically attached to the Mule JARs. This allows you to browse and step into the source code while you’re developing Mule applications. The Mule IDE looks for files with the naming convention mule-*-src.zip in $MULE_HOME/src and automatically attaches them to the Mule JARs.
You may remember that two months ago, I did a webinar on Using Mule and GigaSpaces for Scalable SOA. In this webinar, Uri Cohen and I demonstrate how GigaSpaces XAP could be coupled with Mule to easily take services and make them highly-available.
Another reminder that tomorrow we have a really interesting webinar on how to graphically design data transformations between XML documents and Java objects using Mule. Instead of coding complex XSLT or custom Java classes, you can now simply drag and drop right from the Mule IDE!
Join Francis Upton, creator and Despot of the Oakland Software Data Transformer (OSDT) for Mule and myself for a webinar on Graphical Data Transformation for Mule ESB tomorrow.
Continuing my whirlwind speaking tour on Mule, I landed in Dallas this week to talk to the JavaMUG. This was my first MUG (I’ve been to JUGs, SIGs, Camps, and Meetups, but never a MUG), and I was blown away to walk into a room of 75+ people all there to hear about Mule (okay, the free pizza and soda probably helped, too). Supposedly it was their largest attended event in several years. I gave a similar talk last month in San Francisco, but in Dallas I expanded a little on my thoughts about SOA and the Cloud.
Trying to get budget from the C-level in these economic times can be difficult, but integration and SOA initiatives are still very much alive and need to move forward. Check out this blog post and conversation on ebizQ to consider whether “’Guerrilla SOA’ is a realistic option when the CEO doesn’t approve your budget.”
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.
However, one new offering has caught my eye recently – the Data Transformer for Mule ESB from Oakland Software.
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
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.