4.3.0-20210622
Anypoint Studio 7.10.0 Release Notes
July 29, 2021
What’s New
Anypoint Studio 7.10 introduces a notification mechanism to help you keep up to date with your module’s versions in Exchange. It enables you to propagate metadata to flows and sub-flows, and to rename a flow and have that change refactored automatically to the rest of your project.
Studio 7.10 also improves the dark theme experience and upgrades its underlying infrastructure to Eclipse 4.19.
Components Bundled With This Release
Product | Version |
---|---|
Mule runtime engine |
|
Apache Maven |
3.6.3 |
DataWeave |
2.3.2 |
MUnit |
2.3.5 |
MUnit Studio Plugin |
2.7.3 |
Eclipse |
4.19 |
Maven |
3.3.9 |
AdoptOpenJDK |
JDK 8 (AdoptOpenJDK 8u282-b08) |
API Development Changes
See the following table for the available API development tasks supported by specification type:
Task | RAML | OAS 2.0 | OAS 3.0 |
---|---|---|---|
Create API specifications from scratch |
Yes |
Yes |
Yes |
Create API implementations by importing API specifications |
Yes |
Yes |
Yes |
Import API specifications from API implementations |
Yes |
Yes |
Yes |
Edit API specifications or fragments in Studio |
Yes |
Yes |
Yes |
Retrieve changes from Design Center to an API specification imported into Studio |
Yes |
Yes |
Yes |
Push changes from Studio to an API specification imported and synchronized with Design Center |
Yes |
Yes |
Yes |
Scaffold a new flow from an API specification |
Yes |
Yes |
Yes |
Publish an API specification as an asset to Exchange |
Yes |
Yes |
Yes |
Compatibility
Mule Runtime Engine Compatibility
Applications developed in Studio 7.10 are compatible with the following Mule runtime engine versions:
Mule Runtime Engine Version | Compatible |
---|---|
Mule runtime engine 3.8.x |
No |
Mule runtime engine 3.9.x |
No |
Mule runtime engine 4.1.x |
Yes |
Mule runtime engine 4.2.x |
Yes |
Mule runtime engine 4.3.x |
Yes (Bundled) |
UI Compatibility With Application Deployment Targets
Studio 7.10 offers a graphical interface to deploy Mule 4 applications to the following application deployment targets:
Application Deployment Target | Compatible |
---|---|
CloudHub |
Yes |
On-premises Mule runtime engine instances |
Yes |
Runtime Fabric |
No |
Compatibility With Anypoint Platform Installation Options
Studio 7.10 can integrate with the components of the following platform options:
Anypoint Platform Installation | Compatible |
---|---|
US Cloud |
Yes |
EU Cloud |
Yes |
MuleSoft Government Cloud |
Yes |
Anypoint Platform Private Cloud Edition (Anypoint Platform PCE) |
Yes |
Before attempting to connect to Anypoint Platform by using multi-factor authentication (MFA), change the Browser setting from Built-in to Native.
See Configure Studio’s Browser Settings.
Workspace Upgrade Requirements
Anypoint Studio creates workspaces in which you can create and group your projects. By default, the first time you open Studio, it creates a default workspace and holds all your projects in it. Your Mule application projects might not be fully compatible with workspaces created by a different version of Studio.
Projects created using Studio 6.x.x are not compatible with Studio 7 because they are Mule 3 projects.
See Update Workspaces for more information.
Hardware Requirements
-
8GB of memory.
MuleSoft recommends a minimum of 4GB of free RAM available on a developer workstation. As applications become complex, consider adding more RAM. -
2GHz CPU.
-
10GB free hard drive space.
Software Requirements
-
Java Environments:
Studio bundles two different JDKs:-
AdoptOpenJDK 11 (11.0.10_9)
JDK 11 starts and runs Studio and the Mule runtime instance used for tooling. -
AdoptOpenJDK 8 (8u282-b08)
JDK 8 is the default JRE to run Mule projectsYou can configure Studio to start using your preferred JDK version by following the Configure Studio to Use Your Own JDK steps.
See the studio::whats-new-in-studio.adoc for more information.
-
This version of Studio is not compatible with Java 9 or Java 10.
-
Operating Systems
-
macOS 10.12.0 through 11.0.0
-
Windows 10 (64-bit)
-
RHEL 7.0
-
Ubuntu 15.04 or later
-
Running real-time antivirus protection software on your operating system might have a negative impact on Anypoint Studio performance. Although this issue is prominent on Windows, it also occurs on Linux and macOS. Although the steps to solve these performance issues vary depending on your antivirus software, a typical solution is to either allow or exclude the Anypoint Studio and java executables, the Studio install and workspace filesystem locations, or some combination of both. See examples of solutions for McAfee Viruscan, Windows Defender, and Symantec Endpoint Protection. |
Known Issues
-
Toolbar buttons of Views could disappear under some combination of state and actions. (Eclipse Bug #572598)
-
Context help wizard is not styled correctly in dark theme. (Eclipse Bug #532184)
-
Exporting metadata to a sub-flow fails with the error “The Dataweave script generated contains errors and cannot be used to generate custom metadata” when generating an invalid custom type. (STUDIO-16814)
-
The input/output panes of the Transform Message component display an incorrect background color when using the light theme. (STUDIO-16841).
Fixed Issues
Issue | Description |
---|---|
SE-21329 |
Fixed an issue in which Studio 7.7 to 7.9 only showed 101 records in the response of a |
SE-21108 |
Studio now uses Central/East European, Slavic (ISO-8859-2) instead of ISO-8859-2. |
SE-20816 |
Fixed an issue that caused Studio to not show the content of the Transform Message component after importing an existing project. |
SE-20694 |
Fixed an issue that prevented Studio 7.8 and 7.9 from running a working Dataweave script, throwing an |
SE-20170 |
Fixed an issue that caused the Go to referenced flow option to incorrectly reference a similarly named flow. |
SE-19964 |
Fixed an issue that caused an |
SE-19653 |
Fixed issues with scaffolding OAS 3.0 API specifications. |
SE-19463 |
Fixed an issue that enabled Studio to set an unsupported expression in the payload using a Set Payload component. |
SE-19304 |
Fixed an issue that prevented Studio from expanding Maven properties in the |
SE-18995 |
Fixed issues that prevented Studio on Windows from resolving metadata using the |
SE-18081 |
Fixed an issue that prevented Studio from downloading the parent POM file when loading a child project. |
SE-17386 |
Fixed |