I was able to squash some bugs on the IDE since the last snapshot release.
The first bug was related to creating new projects with a non-default Mule distribution. If you have more than one Mule distribution registered in our Mule IDE preferences, you can choose the runtime to use when creating a new project and the project will refer to the proper jars.
Continue reading 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:
Last week I posted about Writing Mule Transformers, this week I’m going to continue with some more advanced features users can take advantage of.
Lifecycle
All objects in Mule have lifecycle associated with them. Lifecycle calls can be added as necessary. For transformers, there are two lifecycle methods that are most useful.
By default the AbstractEventAwareTransfromer and AbstractTransformer both implement the org.mule.api.lifecycle.Initialisable interface. This means that once all bean properties are set on the transformer (if any) the doInitialise() method will be called. This is useful for transformers to do any initialization or validation work. For example, the transformer may need to load an external file resource in order to be able to perform its function, this should be done in the doInitialise() method.
Additionally, transformers may want to clear up resources when the transformer is no longer needed. To do this a transformer just needs to implement org.mule.api.lifecycle.Disposable and implement the dispose() method.
I will be presenting a webinar tomorrow Dec. 9th at 9 AM PT/ Noon ET covering integration between Mule and webapps. It will be a technical walk-through of an example application consisting of two webapps consuming Mule services, one with Mule running inside it. The audience is assumed to have some prior experience developing with webapps and/or Mule.
Here’s the link to register for the webinar:
It’s a holiday season, and we’re happy to give you Mule 2.1.2! This little Santa helper features over 50 bugfixes and enhancements. Even better, it’s hot in our documentation department, with a dozen issues resolved there and major work put into schema annotations for seamless configuration reference info lookup. Some other highlights include:
A bit of history
We created Mule IDE to ease the work when developing with Mule. Along with the work on Mule 2.0 we started work on an updated version of the IDE that would allow you to graphically design Mule configurations. This turned out to be by far more work than initially expected so we decided to rescope the work. Right now we focus on the little helpers that make developing with Mule easy and cut out the graphical editor for now.
Transformers in Mule are simple objects that convert the current message from one type to another. The interface for a transformer is simple, but there are some tips and tricks for getting the most out of transformers. For this post we will define a transformer the converts from an Order object to HTML so that we can email the details of an order to a customer.
Continue reading