Contact Us 1-800-596-4880

Anypoint Code Builder Release Notes

logo cloud IDE Cloud IDE

logo desktop IDE Desktop IDE

Open Beta Release: The cloud IDE is in open beta. Any use of Anypoint Code Builder in its beta state is subject to the applicable beta services terms and conditions, available from the IDE.

Use the Anypoint Code Builder integrated development environment (IDE) for your API designs, implementations, and integration development. Work locally with Anypoint Code Builder for Desktop on Microsoft Visual Studio Code (VS Code) or from your browser with Anypoint Code Builder on Anypoint Platform. The IDEs support the development lifecycle:

  • API specification design (OAS or RAML), a mocking service for testing, source control, and publication to Anypoint Exchange

  • API implementation features for importing supported API specifications (OAS, RAML, and GraphQL) and autogenerating interfaces (scaffolding) for flows and error handlers within a Mule application

  • Integration development to connect systems, transform data to required formats, and provide business logic to manage messages and events programmatically within a Mule application

February 14, 2024

Anypoint Code Builder releases new features in the Anypoint Extension Pack and the cloud IDE.

  • Extension pack version: 1.0.7

    To use this extension pack in the desktop IDE, see Set up the Desktop IDE.

  • Cloud IDE version: 1.1.3

    This cloud IDE version runs the 1.0.7 extension pack.

For extension versions, see Change Log in the VS Code Marketplace.

What’s New

The release introduces the following features:

Component Configuration Panel in the UI

Anypoint Code Builder introduces a configuration panel in the UI for components, such as connector operations, within integration and implementation projects. This feature simplifies component configuration.

The component configuration panel provides configuration options that are also available through the configuration XML files for your projects. Some components and fields continue to require configuration through the XML in this release. Continue to use XML for complex fields, identified as read-only fields in the UI, and for global configurations, such as connection configurations.

You can open the configuration panel from the canvas or from a configuration XML file within your project. See Add a Component to Your Project and Open a Component in the Canvas from the XML Editors.

Integration Project Creation from Templates and Examples

Anypoint Code Builder adds the ability to import a template or example from Anypoint Exchange into an integration project within Anypoint Code Builder. After importing, you can continue to develop your integration. For information about templates and examples in Exchange, see Asset Types.

For guidance with importing from Exchange, click the tab Start with a Project Template or Example in the procedure Create an Integration Project.

API Design Project Improvements

This release introduces improvements and simplifications to the design process:

  • Import API design projects from Design Center into Anypoint Code Builder. For details, see Import an API Specification from Design Center.

  • Publish your API specifications and fragments to Anypoint Exchange without first syncing your code changes with the Anypoint source control management (SCM) system.

    Creating an API design project from scratch in Anypoint Code Builder no longer spawns a corresponding design project in Design Center or creates a connection to the Anypoint SCM. For details, see Source Control for API Design Projects.

  • Set a business group for your API design project when you publish to Exchange instead of when you create the design project. For example, see the steps in Publish an API Spec to Exchange.

Configuration XML File Creation Enhancement

Anypoint Code Builder enables you to create one or more additional configuration XML files from within your integration or implementation projects. This feature is useful for adding an implementation for an interface. The feature also enables you to split complex project code into more manageable pieces. For more information, see Create an Additional Configuration XML File.

For more information, see Known Issues and Compatibility.

December 6, 2023

Anypoint Code Builder releases a patch to Anypoint Extension Pack and the cloud IDE.

  • Extension pack version: 1.0.6

    To use this extension pack in the desktop IDE, see Set up the Desktop IDE.

  • Cloud IDE version: 1.0.3

    This cloud IDE version runs on the 1.0.6 extension pack.

The patch addresses the following issues:

Description Issue

When you open the IDE, the exception dw-lang-server-language-0" java.lang.NoClassDefFoundError: org/jboss/shrinkwrap/resolver/api/maven/Maven in the Mule DX Server logs no longer occurs because of an open workspace that contains a non-Mule project, such as an API spec project or other folders or files.

W-14268344

The issue java.io.FileNotFoundException no longer occurs due to attempted parsing of files that do not exist.

W-14254505

After scaffolding an API spec into an interface within an implementation project, the IDE no longer produces the syntax validation issue Configuration type reference is not compatible (INVALID_CONFIG_REFERENCE) within the configuration XML for config-ref attribute-value pairs. Previously affected components include <http:listener/>, <apikit:router/>, and <apikit:console/>.

W-14243529

A test connection no longer fails with the error 'Invalid Connection ElementDeclaration is declaring an extension: 'HTTP' that is not part of the session: '[]' after you copy and paste an HTTP Listener configuration (<http:listener-config/>) into a new project.

W-14252415

For more information, see Known Issues and Compatibility.

October 19, 2023

Anypoint Code Builder releases a patch to the cloud IDE:

  • 1.0.2 (Cloud IDE): The cloud IDE removes the proxy for security purposes. URLs that trigger flows in the cloud IDE through the proxy no longer work. To trigger locally hosted flows that use an HTTP listener, see Triggering Flows in Your Development Environment.

There are no changes to the desktop IDE, which remains version 1.0.5.

October 16, 2023

Anypoint Code Builder releases these versions:

  • 1.0.5 (Desktop IDE): Anypoint Code Builder for Desktop (desktop IDE) is generally available (GA) in this release.

  • 1.0.1 (Cloud IDE): The cloud IDE for Anypoint Code Builder remains in open beta:

    Any use of an Anypoint Code Builder IDE in its beta state is subject to the applicable beta services terms and conditions, available from the cloud IDE.

The desktop IDE version 1.0.5 and cloud IDE version 1.0.1 both run on the same versions of the Anypoint Code Builder extensions, described in Change Log, and provide the same features.

To set up and gain access to the IDEs, see Getting Started with Anypoint Code Builder.

What’s New

This release introduces:

Open Beta

Prior to the Oct 16, 2023 release, MuleSoft released these open beta versions of Anypoint Code Builder:

September 2023 (Open Beta)

This update to the open beta introduces Anypoint Code Builder for Desktop on Windows and new features for desktop and cloud IDEs.

August 2023 (Open Beta)

This update to the open beta introduces Anypoint Code Builder for Desktop on MacOS and a new feature for desktop and cloud IDEs.

  • Anypoint Extension Pack on Visual Studio Marketplace to support API specification design (OAS 3 and RAML), API implementation, and integration development

    Install the pre-release_version. Attempting to install the _release version produces an error.

  • Support for the Mac operating system running on Intel or ARM (M1 or M2) processors (see Compatibility)

  • Desktop and cloud IDE support for the following features:

June 2023 (Open Beta)

The update to the open beta for the web-based IDE introduces these features and improvements:

  • Support for EU Cloud: EU Cloud users of Anypoint Platform can now use Anypoint Code Builder from their management plane.

    See Getting Started with Anypoint Code Builder for more information.

  • Synchronization between a local API specification and Mule project: You can now work on your API specification and its Mule project implementation simultaneously.

    Anypoint Code Builder enables you to scaffold your API specification into a Mule project without publishing it to Exchange. You can work on your Mule project, then edit the API specification, and re-scaffold it to reflect your new changes. Both API design and API implementation tasks are now synchronized. You can then publish your API specification and deploy your Mule project from there.

  • Updated UI canvas and code snippet support:

    • Directly import connectors from the canvas instead of using the dedicated command.

    • Use code snippets. See Working with Code Snippets for more information.

April 24, 2023 (Open Beta)

The update to the open beta for the cloud IDE introduces a number of features and improvements:

  • Anypoint Code Builder migrated to a new underlying architecture.

  • The URL for your cloud IDE instance changed. You can get the new URL by launching the cloud IDE from the central page or checking the IDE details.

  • Your session cookie changed, so you must update it when pinging a locally deployed application from a REST client.

April 2023 (Open Beta)

The update to the open beta for the cloud IDE introduces these features and improvements:

  • Business group support enables you to control access to resources when working with assets from Anypoint Exchange. See anypoint-code-builder::business-group-support.adoc.

  • Search filters enable you to refine your search results when looking for an API asset from Anypoint Exchange. See Filtering Search Results for more information.

  • The canvas UI enables you to add components to flows in your integration.

Compatibility

The latest release is compatible with these applications and services:

Application/Service IDE Version

Anypoint Platform

Both IDEs

US and EU clouds only (not supported by MuleSoft Government Cloud or Anypoint Platform PCE at this time)

CloudHub

Both IDEs

1.0 (for deployments to the Sandbox environment)

code-server

Cloud IDE

v4.17.0 (built-in)

DataWeave

Both IDEs

2.4.0-20231211 (built-in)

Java

Both IDEs

Adoptium Temurin (based on OpenJDK) jdk-11.0.19+7 (built-in)

Maven

Both IDEs

3.8.8 (built-in)

Mule runtime engine

Both IDEs

4.4.0-20231211 (built-in)

Operating system

Desktop IDE

Mac OS Intel and ARM (M1 or M2), Windows 10

Visual Studio Code

Desktop IDE

Minimum version: 1.76.1
Tested versions:

  • 1.82.2 (Mac)

  • 1.82.0 (Windows)

Web browser

Both IDEs

Browser Support for Anypoint Platform

Known Issues

The latest release has these known issues and workarounds:

Limitation ID

When the desktop IDE launches for the first time, a corrupted dependency (.m2\repository\net\minidev\accessors-smart\1.2\accessors-smart-1.2.pom) can block the Anypoint Code Builder - Integration Extension when extracting the Mule runtime operation.

Workaround: Delete the dependency from .m2\repository\net\minidev\accessors-smart, and re-launch the IDE.

W-14047707

When launching the cloud IDE for the first time from Anypoint Code Builder, you must allow popups.

None

The list of trusted authors for a directory or file is not persistent across different browsers.

W-12408476

The UI does not provide a notification after you change the region in settings.json.

W-13184670

Due to unfinished internal processing, the error message Mule DX API Component was not installed often occurs after you click Design an API from the Anypoint Code Builder panel in the IDE.

Workaround: Wait for the processing to complete. See Mule DX API Component Was Not Installed for more guidance.

W-14096381

The API Console ignores examples that are defined in a JSON schema.

W-14096158

There is no command to delete dependencies related to assets that you import from Exchange to an API design project.

Workaround: Remove the dependency from the dependencies node in the exchange.json file.

W-13822075

Moving the editors while searching for components from the UI canvas causes your search to be canceled.

Workaround:
Avoid rearranging your editors when using the component palette in the canvas.

W-13172200

Using autocompletion to create a parameter for the value field in the XML adds an extra #[] statement.

W-12444650

Autocompletion does not work properly when more than one connector has the same prefix.

W-10667510

Anypoint Connector for Apache Kafka (Apache Kafka Connector) does not display the Test Connection option.

W-12553536

When you import a Mule project from Studio to Anypoint Code Builder, a DataWeave expression can produce syntax errors (identifiable by a red, wavy underline) in the configuration XML. The issue occurs because the IDE’s tooling is unable to automatically fetch the required dependencies from Mule runtime when the project loads.

Workaround: In the pom.xml file for the imported project, add this dependency as a child of the <dependencies/> element:

<dependency>
  <groupId>com.mulesoft.services</groupId>
  <artifactId>mule-service-weave-ee</artifactId>
  <version>2.4.0-20221212</version>
  <scope>runtime</scope>
</dependency>

W-14037343

DataSense doesn’t identify functions provided by a connector.

W-12448776

DataSense doesn’t reflect array structures at the payload’s root level.

W-12263085

DataSense doesn’t work when a tag spans multiple lines.

W-12482310

DataWeave doesn’t recognize the larger context to which samples belong. So DataWeave requests sample data for all scripts within a single component.

None

DataWeave validations to produce Invalid input errors on some multiline scripts because Anypoint Code Builder does not decode Unicode characters for new lines in XML (&#10;). This limitation does not interrupt the correct execution of your Mule application.

W-11750473

Code highlighting breaks when you define a DataWeave multiline expression. This limitation does not interrupt the correct execution of your Mule application.

W-11492623

Ending a second thread in a Scatter-Gather component before the first thread finishes freezes processing in Anypoint Code Builder.

Workaround: Manually select the other thread to continue processing.

W-10601367

Updates to metadata in one component don’t trigger metadata validation in subsequent components. This issue causes Anypoint Code Builder to display potential issues in the subsequent components.

W-12215165

The Batch Job processor is not supported by the UI canvas or through auto-complete in the configuration XML.

None

See Also