Today we’re releasing Anypoint Studio October 2014, Mule 3.6.0 – Milestone 2 (M2), and Mule 3.5.2. This release includes new HTTP capabilities which make it easy to connect to RESTful APIs with RAML, and productivity enhancements inside Anypoint Studio – such as DataSense for APIkit and a new Studio launcher.
Designed to provide a more pleasurable and productive integration development environment, you can customize your IDE experience with different creative, colorful themes. Choose from among several themes available for download within Anypoint Studio™, Mule’s Eclipse-based IDE.
Our in-house UX team continues to work around the clock to improve Studio’s usability, and capitalize on existing intuitive functionality. Faced with the intense challenges of designing the interaction for a new product and a completely new platform, they decided to distract themselves with relatively simple chore of improving the IDE. It’s already a pretty amazing tool, though, so making it even better was going to be kinda hard.
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.
The old-fashioned way to do this is via the Eclipse Update Manager, using the update site http://studio.mulesoft.org/3.4/plugin:
Every so often, while using Studio, I come across clever little gems that our team thoughtfully inserted into the product to improve usability. These gems don’t get a lot of fanfare, nor do they often warrant much attention on their own, but put together, they make for a smoother, intuitive user experience. Nearly invisible, they have become nearly indispensable to me.
#1 Wrap in and Extract to
It has now been nearly a month since Mule 3.4 was released and coming back from the 8 city tour Spring 2013 Mule summit, I can truly say there is tremendous excitement within the Mule community around the great features that this release offers.
In the coming weeks, key members of the MuleSoft team who were behind this release will be blogging about its various features and capabilities. Here is what this blog post line-up looks like:
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:
- You can download the Mule Studio 3.4 Beta distribution here.
Mule Properties and FLow Variables are one of the most widely used features in Mule. Nevertheless, Mule newcomers may have a hard time understanding how the different property scopes and variables compare to each other, and how to choose the right one for their use cases.
The idea behind this blog post is clarify those differences, comparing side by side INBOUND, OUTBOUND, INVOCATION and SESSION property scopes. We will also cover “flow variables” and “session variables”. For more detailed information, you can go to each scope´s section in the User’s Manual.
Think an easier, more accessible way to build applications is only a dream?
With the release of Mule Studio, the graphical design tool for Mule, integration will never again be the same. Mule Studio is, by far, the easiest and most accessible way to build integration applications. Mule Studio also has no secrets, which means you have full control over the code for ease of use and flexibility.
Mateo Almenta Reca, Director of Product Management at MuleSoft, will take us through the functionality and highlights of Mule Studio, with demonstrations and focus on: