Eclipse users have always felt at home in Mule Studio, but users have often asked for Studio to “play well with others” — specifically, that it support plugin-style installation into existing Eclipse environments they already use every day.
With Mule Studio 3.4, we have delivered this wish list item. Specifically, users of Eclipse 3.8 can now install Mule Studio as plugins into their existing environments.
The old-fashioned way to do this is via the Eclipse Update Manager, using the update site http://studio.mulesoft.org/3.4/plugin:
Today we are happy to announce the beta release of Mule 3.4. This release of Mule ESB and Studio bring together a large set of innovative features that together greatly improve developer productivity, add powerful capabilities for the development of SaaS integrations, and continue to strengthen Mule as an optimal integration platform for the new enterprise.
Before walking through the exciting set of new features that are in this beta, you should know that the release is available for download publicly as follows:
We are pleased to announce the Beta Milestone 5 release of Mule Studio, the graphical design tool for Mule ESB. At its core, it is based on the Eclipse Development Platform which many developers are already familiar with. But we have added significant functionality to it to achieve a very tight integration to Mule ESB. This makes Mule Studio a powerful visual and coding environment for developing Mule ESB applications.
In May we made Mule Studio Beta publicly available, the graphical design tool for Mule ESB. This week we are releasing a new beta milestone, with a lot of fixes and improvements based on your feedback.
For this milestone we focused in two main areas, adding support for Mule functionality towards a complete Mule Studio by GA and easy of use.
Some of the new features in this milestone include:
- Support for Message Enricher
- Security SSL configuration support for HTTP and SMTP
- 5 New Endpoints (Ajax, JDBC, SMTP, Quartz and SFTP)
The second area of focus is easy of use and productivity, some of the improvements includes:
- XML view code completion and auto-import of XML Schema
- Validation and tooltips for property dialogs
Mule configuration files are Spring XML files by nature. So the XML editor is an important development tool and provides a lot of benefit. When working in Eclipse, it provides:
- Schema documentation assistance for the element you are configuring
- Validation of your schema and context of any errors that are detected
- Autocomplete of elements and attributes based on what is valid in the current element of configuration you are editing
However, Eclipse’s XML editor (provided as part of the WTP project) does not properly handle autocomplete with schema substitution groups. Unfortunately, we use those substitution groups a lot in Mule so we filed a bug with the Eclipse project. Half a year later someone attached patch to address the issue. Since then there was not much activity on the issue with respect to getting the fix into an Eclipse release.
As part my work on Mule IDE I sat down and created an update site that you can use to install the patch from. Our list of favorite Eclipse XML editor bugs has the update site links.
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 Tuesday night’s demonstration of the MuleSoft’s Eclipse Tool Suite at the Vancouver Eclipse Demo Camp went well. I almost got Nerf-gunned for a (slight) overtime but the organizers’ mercifulness has allowed me reach the end of the demo with a running sample 🙂 For those who weren’t there, here is a summary of my presentation.
The challenge I’ve set to myself for this demonstration was the following: let’s figure out what’s the total length of roadworks currently happening in the city of Vancouver. Think of it as a reality check for your tax dollars at work!
Because Vancouver exposes plenty of its data on the web, this was really just a matter of pulling the right data source and transforming it to the desired output. Read on to find how I achieved this using Mule Data Integrator and Mule IDE…
For those of you who develop in Eclipse, and are also running Tomcat as a stand-alone JVM process (the way Tomcat is usually run), it is fairly easy to debug your web applications using the Eclipse debugger. For that matter, you could also debug Tomcat’s code this way as well, if you want to inspect what Tomcat is doing with a request.
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.