When an issue arises in production it can be quite daunting to reproduce it in a test environment. Ideally one debugs the live application. But logs don’t tell the whole story. And a severe issue may require the application be taken down. How can it be stopped and debugged at the same time? With Mule composite sources and Mule Management Console (MMC) end-point control you can eat your cake and have it,
Mule 3 defined a simple, universal structure for Mule ESB applications. It’s a simpler version of war file format, consisting of a zip file with three sorts of entries:
- At the top level, configuration files and application properties files
- In the lib directory, jar files
- In the classes directory, classes and resource files
We also created a maven plugin to build Mule apps.
How many web sites/web services have you wished you could just interact with over the command line? Sometimes, you just want to type commands in your shell. I can name at least 3 of our products which I’ve wished I could do that with: iON, MMC, and Tcat.
There are some challenges though. Bash/BAT file scripts don’t provide facilities to interact with web services. Then, if you go with a cross platform language,
I’m really happy to give you more details about Mule Studio. This is a project that started early last year and we are finally getting to a point that we are ready to share a first beta version with the entire Mule Community.
Mule Studio is an Eclipse-based developer tool, that allows to graphically create and test Mule ESB Flows.
The Mule IDE does not natively support Mule 3’s new application structure yet, but not to worry, with the new 2.1 release of the Mule IDE you can still keep it hot when working in the IDE. Just follow a few simple steps and your apps will be doing the tango with Mule 3 while you code away in Eclipse.
Last week at the Mule Summit, I gave a presentation on Mule IDE. One of the questions from the audience was about putting your own examples in the “Sample content” drop down on the “New project” dialog.
This is actually possible today. Here is how you do it:
We have just released version 2.0.1 of Mule IDE. This release provides an important bug fix (the new configuration wizard no longer overwrites existing files without prior notice). It also provides support for the new Mule Data Integrator, which is about to be released.
MuleSoft is proud to announce that Mule IDE 2.0 has been released.
Mule IDE 2.0 is a development and testing environment based on Eclipse. It supports the following features:
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.
If you’re evaluating Mule Enterprise, the source code is not included with the Mule download.
Today I released the 2.0 RC1 release of the Mule IDE. Not much changed since the last development snapshot but we have tested the IDE a lot internally on a variety of operating systems since then.
If you upgrade from a development snapshot, note that you’ll have to change the location of the update site: the snapshots were located under the snapshots distribution area but the new milestone release is located under .