Nav

Anypoint Studio June 2015 with 3.7.0 Update Site 1 Runtime Release Notes

July, 2015

This July 2015 release is a first update to the Studio July 2015 with 3.7.0 runtime.

Current Release Versions

Enterprise Runtime Community Runtime

ESB Runtime

3.7.0 EE

3.7.0 CE

Anypoint™ Studio

Version: 5.2.1
Build Number: 201507311055

Management Console

n/a

Mule DevKit

3.7.0

APIkit

version: 1.7.0

New Features and Functionality

  • DataSense support for RAML resorces with a mime type of application/x-www-form-urlencoded

  • DataSense support for JSON samples defined in RAMLs

  • DataWeave editor improvements

  • Support for mocking inputs when metadata is not defined

  • Fixed issue with escaping object keys that start with an underscore

  • Fixed issue with scaffolding repeating elements

  • Improved Debugger performance

  • Many more bug fixes

Migration Guide

This section presents configuration considerations you may want to adjust when migrating from a previous version of a Mule runtime, or previous version of Studio. Contact MuleSoft if you have a question about a specific migration activity or concern.

  • Mule ESB 3.7.0 is supported from Anypoint Studio June 2015 Release and onwards. Older Mule ESB runtimes can also be installed in the new Anypoint Studio release.

  • APIkit 1.5.1 only works in runtimes whose versions are less than 3.6.0. APIkit 1.6.0 works in the 3.6.0 runtime and above (see JIRA STUDIO-5955).

  • Java 7 is required for Anypoint Studio. If you are deploying to Java 6 runtimes, you can continue to configure Java 6 as the Java runtime for your project. Note: If you are installing Anypoint Studio on a new computer or a fresh installation, you must also download and install JDK 1.6, which provides important libraries for later JDK versions. Install JDK 1.6 first and then install JDK 1.7. Note: If you are installing Anypoint Studio on a new computer or a fresh installation, you must also download and install JDK 1.6, which provides important libraries for later JDK versions. Install JDK 1.6 first and then install JDK 1.7.

  • If you wish to install a previous runtime or a community runtime, follow the instructions to add additional runtimes to your new instance of Studio.

  • From the previous versions of Studio (5.1.1, 5.2.0) 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.

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.

import

Then specify the location of your old version of Anypoint Studio in your local drive.

Hardware and Software System Requirements

  • The 3.7.0 release does not change the hardware and software system requirements established by the 3.6.1 Runtime.

  • MuleSoft recommends a minimum of 4 GB RAM on a developer workstation. As applications become complex, consider adding more RAM. Contact MuleSoft Support with any questions you have about system requirements.

Deprecated in this Release

  • Nothing was deprecated in this release.

Bug Fixes

Issue Description

STUDIO-5569

Debugger does not display record variables in Batch Jobs

STUDIO-6014

NullPointerException thrown when creating and running a Studio (Maven) Run Configuration

STUDIO-6523

Metadata generation from example is not working for some XML (Example enclosed)

STUDIO-6667

Debugger Not possible to debug correctly when using a Scatter-Gather MP

STUDIO-6778

Fixing issue in scaffolding when there are repetitive elements at different levels

STUDIO-6780

SE Spring property child element is lost when two way editing

STUDIO-6783

Studio does not let users to upload an application to cloudhub referencing a custom domain

STUDIO-6784

Templates/examples import not adding custom metadata

STUDIO-6789

Custom Metadata Explorer displays default type for components that don’t have operations

STUDIO-6794

DataSense output propagation not working when resources has both input and output of the same type

STUDIO-6806

DataWeave does not support keys starting with underscores

STUDIO-6807

There is no Run option for Maven projects when Maven is disabled

STUDIO-6808

Studio Debugger Performance issue

STUDIO-6810

Cannot use Mule with Maven run configurations built from scratch

STUDIO-6814

SE DataMapper hangs with a particular project

STUDIO-6815

SE Delimiter bug in DataMapper ^

STUDIO-6818

SE Attribute stateful is invalid Quartz inbound and outbound endpoints

STUDIO-6819

SE Invalid required attributes in IMAPS TLS configuration

STUDIO-6821

Certain editors through NPE when trying to set default value for radioBoolean

STUDIO-6824

Transform: Can’t specify input sample data format when there’s no metadata

STUDIO-6825

Partial deployment of domains is not working

STUDIO-6830

"Search Exchange for…​" link is broken

STUDIO-6831

Scaffolding Problem when scaffolding JSON arrays in Transformer MP

STUDIO-6838

Content type text/json and text/ xml are not recognized by RAML parser

STUDIO-6839

HTTP Request When Raml file does not have any response declared, a wrong warning is displayed.

STUDIO-6849

Multi Level Keys Datasense retrieval is being triggered even when not all elements are populated

STUDIO-6850

Finish button in Deploy to Cloudhub window is always disabled

STUDIO-6852

Can not run functional test case with DataWeave or DataMapper

STUDIO-6854

Multi Level Keys Refreshing Metadata when no key is configured shows a SAXParseException instead of a bad key error

Improvements

Issue Description

STUDIO-6785

HTTP Connector doesn’t support datasense when RAML contains body of type application/x-www-form-urlencoded

STUDIO-6793

HTTP Connector support for Json example in order to create metadata

STUDIO-6805

Generate XSD from XML sample in HTTP connector if RAML only has examples

STUDIO-6841

A proper warning should be shown when multiple inputs or outputs are present in a RAML Support Resources