A couple of weeks ago, we released the first Mule 3.4 Early Preview which introduced a whole set of new features; in this second pre-beta release, we have further stabilized the new features and added a few more. Just to recap, the list below enumerates the highlights of the the first Early Preview release:
- Visual Flow Debugging
- Connection Management
- Documentation Generation
- DataMapper Enhancements
This second early preview has incorporated early-adopter feedback and offers even more!
Upgraded Studio base Eclipse version
Studio now runs on Eclipse 3.8, incorporating all bug fixes and enhancements this new version provides. (All previous Studio versions were sitting on Eclipse 3.6). As well, this release supports JDK 7 under Mac OSX and includes the formal fix for the junit launcher in Windows. (Previously, junit failed to execute because of the long length of the command line).
Complete Visual Flow Debugger
Visual Flow Debugger is done! First and foremost, you no longer need to add the custom agent code in your configuration file as with the first Early Preview release. The following piece of code is no longer required:
We have now enabled Remote Debugging. You can start your standalone Mule server with debug mode enabled, then connect from Studio to debug your application remotely using the new Remote Mule Application configuration.
Use the following command lines to start your Mule server:
When stepping through your flow with the debugger, you can change the value of the Mule message (for example, the payload). This is really useful when you want to correct a value before running the rest of the flow.
Studio projects that you ran in the embedded Mule server were always built by Studio itself. Now you can use Maven to build your project, allowing you to run/debug the application as you would with the mvn command line. Further, every time you drop a component into the canvas, Mule updates the pom.xml file automatically with all Cloud Connector dependencies.
DataMapper Enhacements II
DataMapper scripting language, originally based upon CTL, now uses Mule Expression Language (MEL) by default. This simplifies the syntax and ensures expression consistency across the product . For ease of use, the new script editor supports auto-completion.
In the past, DataMapper was not able to create concrete instances of Interfaces or Abstract classes when present in the destination POJO. Now users can either create bindings or define a POJO factory to create concrete instances in the output.
Other nice features include:
- improved streaming support
- support for recursive XML structures
- regeneration (reload) of schema information (for example, when updating the sample CSV file used to define schema)
As we continue to work hard to deliver a better, more solid Studio, we want your feedback! We still have time to improve the product before GA, so if you find any bugs or think we can improve the features, feel free to file a JIRA or use our forums.
Download the Mule Studio 3.4 Early Preview (See the lower part of the page under ‘Milestone Releases’) and send us your thoughts. We look forward to hearing from you!
No related posts.