Anypoint Studio 5.3.0 With Mule Runtime 3.7.2 Release Notes
September 17, 2015
Build ID: 201509170844
Compatibility
Mule Runtime
Version: 3.7.2 EE
Anypoint Studio
Version: 5.3.0
Build Id: 201509170844
APIkit
Versions: 1.6.2 - 1.7.2
SAP Connector
Versions: 2.1.2 - 2.2.7
DataWeave
Version 1.2
Features
-
A new Validations Module allows you to easily validate Mule messages using a variety of built in validators.
-
You can now attach sources for JARs bundled inside Mule runtime containers on the classpath, and Anypoint Studio remembers the settings. You can also reference Mule flows contained in JARs on the classpath.
-
Added preference pane that allows users to manage the location of their Mule source zip files and attach them to Mule runtimes.
-
Anypoint Studio now auto-creates a project with the API Gateway default domain that contains a shared HTTP listener configuration for all your APIs.
Hardware and Software System Requirements
-
For most use cases, Anypoint Studio with the 3.7.x Runtime does not change hardware or software requirements.
-
MuleSoft recommends a minimum of 4GB RAM on a developer workstation. As applications become complex, consider adding more RAM.
-
This version of Anypoint Studio requires Java 7. Note: If you are installing Anypoint Studio on a Mac computer with OS X that has no Java installed, the OS may require that you first download and install JDK 1.6. Install JDK 1.6 first and then install JDK 1.7.
Migration Guide
From the previous versions of Studio (5.1.1, 5.2.0, 5.2.1) there is no special migration needed, but when coming from older versions, it’s recommended that you create a new workspace to host projects built with this new version. When opening a previous Workspace with projects that were created with Studio 5.1.0 or older, and which has metadata stored in disk, Studio asks you to perform an update to all the projects so that the Metadata Manager can handle the types and to show the types in your project. Note that performing this conversion might imply loosing previously defined run configurations.
| Studio as an Eclipse plugin only works with Eclipse 4.3 or 4.4 due to an SWT dependency. |
|
You can easily import all of the external components that you had installed in your old version of Anypoint Studio through a single action. This includes connectors, runtimes, and any other type of extension added through the Anypoint Exchange or the Help → Install new software menu, as long as there are no compatibility restrictions. Do this by selecting File→Import and then choose Install→From existing installation. 
Then specify the location of your old version of Anypoint Studio in your local drive. |
Known Issues
-
Error highlighting in the XML view sometimes does not properly refresh until you go to the Message Flow view and back to the XML view. (STUDIO-7027)
-
When API Gateway runtime version 2.0.0 and newer is not installed in Studio, you cannot choose between 1.3.2 Gateway or 3.7.2 Mule runtimes. (STUDIO-7064)
Eclipse Plugin
If you are using Studio as an Eclipse plugin, you can get this version of Studio using the Eclipse update site http://studio.mulesoft.org/r4/plugin.
This allows you to download Anypoint Studio core and third-party components version 5.x.x and with an embedded version of Mule Runtime v3.7.x along with other optional components.
For a detailed description of the update site’s content visit the Studio in Eclipse section.
Bug Fixes
| Issue | Description |
|---|---|
STUDIO-1311 |
Able to drag and drop composite source and poll as response elements |
STUDIO-1438 |
Two-way editing - In spite of the fact that service-overrides is not supported by the UI, when adding it manually it is sorted in a wrong way that the app fails if you run it |
STUDIO-2718 |
Flow ref editor should be alpha sorted and allow filtering |
STUDIO-2720 |
Support for referencing external resources |
STUDIO-3606 |
Mule Runtimes miss source code of open source libraries and prevent linking source code |
STUDIO-4535 |
HTTP XML Validation - When Port is not specified in XML, default is used, but XML is marked as error |
STUDIO-5909 |
Leaving focus from HTTP endpoint marks mule config as not saved |
STUDIO-6158 |
Attribute Type is required' message even when it is populated |
STUDIO-6206 |
Studio Login - Deploy to CloudHub should validate Domain projects first |
STUDIO-6312 |
Transform: Pressing the keys Ctrl+Backspace or Option+Backspace in the input editor generates errors |
STUDIO-6572 |
Keyboard shortcuts do not work in most of the Text Fields |
STUDIO-6607 |
Problem with Editor’s Colors in Linux |
STUDIO-6614 |
Create new mapping button isn’t aligned |
STUDIO-6625 |
Scroll bar in What’s new dialog in Linux |
STUDIO-6630 |
Deploy to CloudHub: Error when retrieving list of Domains |
STUDIO-6714 |
Maven projects should recognize the finalName element |
STUDIO-6722 |
Transform: problem with type inference |
STUDIO-6757 |
CXF connector not working on WSDL configuration from a file |
STUDIO-6773 |
Studio allows to deploy an app with an IPV4 port already in use |
STUDIO-6813 |
Version attribute in the Mule config is not updated when changing the runtime |
STUDIO-6817 |
Conflicts exporting a Gateway Runtime application with API Gateway Domain associated |
STUDIO-6826 |
Evaluate Mule Expression should have history |
STUDIO-6827 |
ErrorSense - NPE in Choice properties editor |
STUDIO-6842 |
Runtime labels are not correctly displayed after installing GW runtimes from update site |
STUDIO-6855 |
Studio is not parsing Iterator or Iterable |
STUDIO-6858 |
NPE when opening Run Configurations |
STUDIO-6877 |
Run as Mule App missing after deleting the pom file in a maven based project |
STUDIO-6879 |
Transform: you are prompt to delete associated files when the script is inline |
STUDIO-6900 |
Remove invalid attribute jcoIdleTimeout from SAP connector |
STUDIO-6907 |
APIKit menu entry rows on none mule projects |
STUDIO-6909 |
Incorrect validation for nested context in HTTP Listener config in domains |
STUDIO-6913 |
Query builder issue due to metadata cache changes |
STUDIO-6915 |
Exception in logs when validating maven SAP project |
STUDIO-6922 |
Make Validations MPs contribute VOID metadata to the propagation |
STUDIO-6925 |
Don’t trigger attachment process if I have already triggered it from "Apply" button |
STUDIO-6927 |
Performance Issue when applying changes |
STUDIO-6928 |
Zip files are not recognized in Windows |
STUDIO-6929 |
Metadata namespace is not declared when metadata is set on an endpoint |
STUDIO-6936 |
When creating custom metadata types for a HTTP with headers, they are multiplied |
STUDIO-6940 |
DataSense classloader is not including User Libraries |
STUDIO-6941 |
|
STUDIO-6957 |
Different behavior to select Exception Factory properties |
STUDIO-6958 |
When opening a Transformer MP view which contains Java mappings, an error is thrown |
STUDIO-6959 |
SchemaLocation for Validation is missing |
STUDIO-6969 |
When using Validator: ALL, it is not working because |
STUDIO-6978 |
Double Label "Nested Validators" in ALL Validator window |
STUDIO-6979 |
Authentication tab in HTTP request configuration always shows the pre-emptive checkbox |
STUDIO-6995 |
Mavenize in Windows with empty repo hangs Studio |
STUDIO-6999 |
Remove labels "Message" and "Exception Class" from All validator view |
STUDIO-7001 |
Flow Name in API Autodiscovery dialog should be required |
STUDIO-7007 |
Transform: Fix preview for 3.7.0 and 3.7.1 |
STUDIO-7018 |
SalesForce - No class def Found error when trying test connection |
STUDIO-7021 |
Performance issue when saving app when using DataWeave |
STUDIO-7027 |
Problems in the XML editor remain even when already solved |
STUDIO-7029 |
Analytics: event records of components usage (canvas, global elements creation, etc.) lack the runtime version attribute |
STUDIO-7042 |
Unable to create project with 2.0.2 GW runtime |
STUDIO-7046 |
External References] External configuration elements should not be able to be edited from the UI |
STUDIO-7047 |
Refresh Types" button deletes the associated connectors' types caches structures improvement |
STUDIO-1694 |
Default of "Auto delete" in the File endpoint is hidden in a non-usable way |
STUDIO-5103 |
Add autocompletion support in Debugger "Evaluate Mule Expression" popup |
STUDIO-6036 |
Studio MEL Evaluator should keep the last written MEL expression |
STUDIO-6230 |
Output format dropdown |
STUDIO-6232 |
Reduce the height of bottom tabs |
STUDIO-6235 |
Add a dot indicator to mapped values |
STUDIO-6676 |
Metadata Manager - Autoselection of the type of the file used when doing a metadata type refresh. |
STUDIO-6820 |
Refresh folder schema folder after generating XSD from XML in DataMapper |
STUDIO-6853 |
Studio should propagate metadata correctly for DevKit connectors that return VOID |
STUDIO-6894 |
XSLT message processor properties does not show context-property elements |
STUDIO-6908 |
Select a Message processor from Outline tab |
STUDIO-6910 |
Studio support for Rational source control system |
STUDIO-6960 |
Add Validator icons |
STUDIO-6970 |
Improve look and feel of Add Java Class and Browse Java Class in Class picker editor |
STUDIO-6988 |
Create the api-gateway domain project when importing proxy projects |
STUDIO-6994 |
Improve design of the buttons when selecting a class |
New Features
| Issue | Description |
|---|---|
STUDIO-6337 |
Palette Filtering - Add a preference at a project level to hide common transformers when using runtimes that support DFL |
STUDIO-6801 |
Define experience for attaching sources for enterprise runtimes and third party libraries |
STUDIO-6834 |
Attach enterprise sources zip file for Mule Runtimes |
STUDIO-6862 |
DW-UI - Change Editor Layout |
STUDIO-6919 |
Support for "All" validator |
STUDIO-6933 |
Things to be defined |
STUDIO-6934 |
Transform: Add metadata to flow lookup |
STUDIO-6945 |
Download and attach sources for open source libraries (including the ones in Mule Runtime) for Maven projects |
STUDIO-6971 |
Transform: Set custom metadata through the input tree |
New Stories
| Issue | Description |
|---|---|
STUDIO-2982 |
Combining language components and transformers into as single one |
STUDIO-3404 |
DataMapper is not suitable for low-latency or real-time transformations between same data-types |
STUDIO-6527 |
SOAP Connect generated editor should not display the “Operation” combo |
New Tasks
| Issue | Description |
|---|---|
STUDIO-6516 |
Build and test REST to SOAP gateway scenario |
STUDIO-6671 |
Update What’s New Image |
STUDIO-6672 |
Build End to End scenario App |
STUDIO-6832 |
Make source attachments of Mule Runtime editable |
STUDIO-6889 |
Transform: preview should use the same jar inside the runtime to be consistent between preview and runtime |
STUDIO-6924 |
Restore Defaults button should delete all attachments |