salesforce Dreamforce On-Demand
Contact Us 1-800-596-4880
  1. Homepage
  2. Archived Release Notes

  3. Anypoint Studio 7.4.2 Release Notes

Anypoint Studio 7.4.2 Release Notes

February 6, 2020
Build ID: 202001311805

What’s New

Studio 7.4.2 release includes:

  • Performance to address memory leaks, minimization of background processing.

  • Upgrade of the Eclipse base version from 4.7 to 4.9.

  • Chromium Web Browser.
    Migrated browser integration infrastructure from XULRunner to Chromium for better browser selection based on the operative system native browser to Chromium.* Bug fixes.

Upgrading to This Version

If upgrading to this version from Studio’s update site fails, you must download this new version from the download site and re-install it.

See Downloading and Installing Anypoint Studio.

Components Bundled With This Release

Product Version

Mule runtime engine

4.2.2

Apache Maven

3.3.9

DataWeave

2.2.1

MUnit

2.4.0 (munit-studio-plugin)

Eclipse

4.9.0

Compatibility

Studio Components Compatibility

Studio 7.4 is compatible with the following bundled component/extension versions:

Product Version

Mule runtime engine

4.1.4 and later

Apache Maven

3.3.9
Studio comes with Maven 3.3.9 bundled, but you can externally use the versions: 3.3.3 or your own 3.3.9

DataWeave

2.2.1 and later

MUnit

2.2.0 and later

APIkit

1.3.6 and later

Mule Runtime Engine Compatibility

Applications developed in Studio 7.4 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

UI Compatibility With Application Deployment Targets

Studio 7.4.x 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
You can still deploy to Runtime Fabric by exporting your application in Studio and deploying it separately.

Compatibility With Anypoint Platform Installation Options

Studio 7.4 can integrate with the components of the following platform options:

Anypoint Platform Installation Compatible

US Cloud

Yes

EU Cloud

Yes

MuleSoft Government Cloud

No

Anypoint Platform Private Cloud Edition (Anypoint Platform PCE)

Yes
See configure Private Cloud Edition in Studio for more information.

Projects Compatibility

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 stores all your projects in it. Your Mule application projects can not be fully compatible with workspaces created by a different version of Studio:

Projects created in a Studio 6.x.x or earlier workspace

These projects are not compatible with Studio 7 because they are Mule 3 projects.

Projects created in a 7.1.x workspace

Because Studio 7.2.0 simplified the configuration of the mule-artifact.json file, if you are importing a project created in a Studio 7.1.x workspace, see Updating Workspaces for instructions to update your project structure to a compatible format.

Projects created in a Studio 7.2.x or later workspace

Projects created in this workspace are fully compatible. You can use a project created in a Studio 7.2.x workspace without performing any extra task.

Hardware Requirements

  • MuleSoft recommends a minimum of 4GB of free RAM available on a developer workstation. As applications become complex, consider adding more RAM.

  • 8GB of memory.

  • 2GHz CPU.

  • 10GB free hard drive space.

Software Requirements

Software

Version

Java Environments

  • AdoptOpenJDK 8

This version of Studio is not compatible with Java 9, Java 10, or Java 11.

The only compatibility introduced for Java 11 is when using Mule runtime engine 4.2.0 or later. Studio still requires Java 8 to launch and run properly. You can install and configure Java 11 on your machine, but make sure to configure this JDK to be used by the embedded 4.2.x runtime running in Studio.
See Change the JDK from Studio for instructions on how to do this.

If you are experiencing issues booting up Studio, see the troubleshooting recommendations for Windows, Linux, or MacOS.

Operating Systems

  • MacOS 10.12.0

  • Windows (64-bit)

    • Windows 7

    • Windows 8

    • Windows 10

  • 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

  • MUnit Studio plugin 2.1.5 does not work with this version of Studio.

  • Because the metadata propagation works differently in Studio 7, Datasense might display errors if your DataWeave code has references to unknown metadata either because you didn’t define the metadata before writing your code, or because your flow is still incomplete.
    See Understanding How DataSense Uses Mule Event Metadata and Transform Message Component for more information.

  • As of November 2019, Studio no longer provides binaries.

  • Custom Policies Editor is not yet supported in Studio 7.

  • Copybook import fails with no message.

  • Copybook import file not copied to project.

  • The pom.xml file of a running application is not updated when changing dependencies.

  • The payload shown while debugging a Mule application in the debug view is partial but there is no way to view the rest of the payload.

  • Mule plugins with snapshot versions should always be regenerated.

  • Datasense/Runtime not working correctly through proxy on connectors using TCP/IP or connectors which don’t yet support it.

  • When importing a project with a runtime that is not installed in Studio there is no notification to the User.

Bug Fixes

  • Duplicated namespaces now show as an error in Studio XML configuration file editor.

  • Fixed NullPointerException when right-clicking a project after opening the context menu in the Configuration XML editor and closing the editor.

  • Fixed issue initializing the MULE_LIB/org.mule.connectors/mule-sockets-connector/1.1.1 classpath container for projects wt-4.4.13.

  • Fixed issue on Linux where the Transform Message UI brakes after Edit current target.

  • Fixed error when importing a project created in 7.3.x in 7.4.x.

  • Fixed "Unable to resolve reference …​" errors in Transform Message component editor in Studio 7.2.1.

  • Fixed issue initializing the MULE_LIB in Studio 7.3.5 & Mule runtime engine 4.2.2.

  • Fixed error where Studio shows an error when importing an existing project from filesystem.

  • Fixed error when Studio detected changes when no change was done.

  • Fixed validation errors shown in RAML editor for valid RAML spec.

  • Fixed error where an M2 repository population was executed in every startup adding an overhead specially under windows.

  • Fixed error where updating an API only allowed the user to hit the refresh button once.

  • Fixed error where after updating an API design with a JSON schema and refresh in Studio, the metadata did not work.

  • Fixed issue where deleting the version of a Mule project from Exchange and then publishing if from Studio using the deleted version a 400 status response was thrown.

  • Fixed issue where an exception was thrown for SOAP: Header when using APIkit for SOAP 1.2.3.

  • Fixed issue where Studio ignored the selected Mule runtime engine version when importing project from filesystem.

  • Fixed issue where APIkit scaffolding failed when there was an existing previous file scaffolded.

  • Fixed issue where importing an API as a dependency when updating from runtime 4.2.1 to 4.2.2 failed.

  • Fixed error when resolving metadata when the Maven repository had spaces.

  • Fixed issue where Studio did not load multi-level metadata unless it was saved and re loaded.

  • Fixed issue where opening the "edit" button of a version, the "Cancel" and "Ok" buttons were not readable any longer.

  • Fixed issue where enabling "update snapshots" in studio 7.4 rendered the project unable to run.

  • Fixed issue where Studio did not enable the "Run" button under Run Configuration for applications in old workspaces.

  • Fixed issue preventing users to edit the version of a module.

  • Fixed issue where selecting an API or module in the dependencies view caused the edit button to dissapear.

  • Fixed NullPointerException thrown after adding a configuration to Web Service Consumer module.

  • Fixed issues where metadakeys could not be retrieved when the configuration is located in a domain.

  • Fixed issue where a duplicated debug configuration was created when having a domain project.

  • Fixed issue where projects were copied to the workspace root folder when importing them from a folder inside the workspace.

  • Fixed issue where Studio could not import an API created in Studio 7.3.5 from Exchange.

  • Fixed issue where Studio update sites asked for certificates installation.

Support