Mule Runtime
Anypoint Studio 6.4 with 3.9.0 Update Site 4 Runtime Release Notes
March 27, 2018
Build ID: 201803231844
Compatibility
Version: 3.9.0 |
|
Anypoint Studio |
Version: 6.4.4 |
APIkit |
Versions: 3.9.0 - 3.8.3 - 3.8.2 - 3.8.1 - 3.8.0 - 1.7.4 - 1.6.2 - 1.5.3 |
DataWeave |
Version: 1.2.0 |
MUnit |
Version: 1.6.1 (munit-studio-plugin) |
Eclipse |
Versions: 4.5.2 |
SAP Connector |
Versions: 3.2.0 |
What’s New
This release of Studio 6.4.4 includes mainly bug fixes and support for the Anypoint EU infrastructure.
Migration Guide
For first time installment, please refer to Studio 6.4 release notes for hardware requirements and known issues.
From the previous versions of Studio 5.1.0, 5.1.1, 5.2.0, 5.2.1, 5.3.0, 5.4.1, 5.4.2 and 5.4.3, there is no special migration needed, but 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.
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. |
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/r5/plugin.
This allows you to download Anypoint Studio core and third-party components version 6.x.x and with an embedded version of Mule Runtime v3.9.x along with other optional components.
For a detailed description of the update site’s content visit the Studio in Eclipse section.
JIRA Ticket List for Anypoint Studio
Bug Fixes
-
STUDIO-10499 - When setting the url for on prem configuration in studio, login and other platform interactions are not using that url.
-
STUDIO-10577 - Studio allowing reconnect strategies at endpoint level for 3.9.0.
-
STUDIO-10580 - TRAINING: Error parsing RAML file in HTTP Request connector for Windows.
-
STUDIO-10596 - MultiPageMessageFlowEditor raises an NPE when validating.
-
STUDIO-10604 - NullPointer when validating wmq listener with transactions.
-
STUDIO-10606 - When using a custom policy definition which has a resourceLevelSupported property, the editor displays an error.
-
STUDIO-10607 - RAML Circular Reference generates Anypoint Studio performance and data sense issues.
-
STUDIO-10609 - Logger Category looks like it accepts MEL expression, when it doesn’t.
-
STUDIO-10614 - APIKIT console blocks when a self-signed certificate is used.
-
STUDIO-10651 - Large RAML causes StackOverflow Error in Studio private release 6.4.2 HF1.
-
STUDIO-10655 - DW Does not perform custom object type checking when chaining expressions.
-
STUDIO-10717 - Multiple and unnecessary validations in the flows whose names match the naming convention for a raml coordinate.
-
STUDIO-10750 - Xalan dependency is ignored.
Support
-
Access MuleSoft’s Forum to pose questions and get help from Mule’s broad community of users.