Contact Us 1-800-596-4880
  1. Homepage
  2. Archived Release Notes

  3. Anypoint Studio 7.9.0 Release Notes

Anypoint Studio 7.9.0 Release Notes

April 29, 2021

What’s New

Anypoint Studio 7.9 enables users to use a dark theme, and upgrades its underlying infrastructure to Eclipse 4.18 and Java 11, adding official support for macOS Big Sur.

This version also introduces improvements for Dataweave code experience and enhanced macOS experience by notarizing Studio as a macOS application.

Components Bundled With This Release

Product Version

Mule runtime engine

4.3.0-20210322

Apache Maven

3.6.3

DataWeave

2.3.2

MUnit

2.3.1

MUnit Studio Plugin

2.7.2

Eclipse

4.18

Maven

3.3.9

AdoptOpenJDK

JDK 8 (AdoptOpenJDK 8u282-b08)
JDK 11 (AdoptOpenJDK 11.0.10_9)

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.9 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.9 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.9 can integrate with the components of the following platform options:

Anypoint Platform Installation Compatible

US Cloud

Yes

EU Cloud

Yes

MuleSoft Government Cloud

Yes
See access MuleSoft Government Cloud from Studio for more information.

Anypoint Platform Private Cloud Edition (Anypoint Platform PCE)

Yes
Studio 7.9 can only connect to PCE 3.0.0.
See configure Private Cloud Edition in Studio for more information.

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 projects

      You can configure Studio to start up 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

  • 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.

  • Metadata is not propagated on sub-flows.

  • Toolbar buttons of Views could disappear under some combination of state and actions. (Eclipse Bug #572598)

  • Context help wizard not styled correctly in dark theme. (Eclipse Bug #532184)

  • When using the DataWeave editor and switching from light theme to dark theme (or viceversa), a pop-up appears with a Multiple Errors have Occurred message.

  • MUnit tests with no run configuration do not run if the MUnit test recorder also has a run configuration set up.
    For these tests to run, you must remove your MUnit test recorder run configuration.

Fixed Issues

Issue Description

SE-17411

Fixed an issue with flatFile in an auto-generated schema.

SE-18295

Creating an OData-Enabled API no longer fails if there is a space in the Workspace folder.

SE-18528

Fixed thread deadlock.

SE-18760

Fixed issues with Mac Big Sur 11.0.1.

SE-18810

Fixed an issue with the Email connector being unable to set Content Transfer Encoding.

SE-18819

Fixed additional "{" characters being added in Dataweave when using Anypoint Studio in Mac Big Sur.

SE-18910

Fixed an issue that prevented users from selecting a wsdl for SOAP Configuration.

SE-19043

Renaming a component in Studio no longer deletes it.

SE-19260

Studio Debugger now stops at breakpoints defined for components immediately within a cache scope.

SE-19389

UI error no longer shows up when trying to set scheduler-pools configuration to UBER pool.

SE-19454

Fixed an issue that prevented users from deleting a metadata type when the project belonged to a Mule domain.

SE-19602

Fixed an issue that prevented the logger Dataweave graphical view from showing after enabling expression mode, and the Transform Message component from not showing all fields.

SE-19670

Fixed an issue in which the Java debugger preference was not being respected when debugging from the toolbar or from the project context menu.

SE-19895

Fixed an issue that removed comment blocks from the pom.xml file after publishing the project to exchange.

SE-19955

Fixed an issue that prevented users from deleting the sourceType ANY in the Error-mapping view.

SE-19964

Fixed Invalid Field Value error when using a property inside a drop-down.

SE-20226

Fixed an issue that disabled the format context menu option when opening JSON files.

Support