reuse::partial$beta-banner.adoc
Some Anypoint Code Builder features can be disabled or hidden based on settings in the IDE.
For any features that aren’t working as expected, first check for problems and issues.
If the MuleSoft icon (see start-discover-ui.adoc) is missing from the Activity Bar, check for and address common causes.
The Activity Bar allows you to enable or disable icons.
-
In the IDE, right-click the Activity Bar.
-
Check for Anypoint Code Builder:
-
If Anypoint Code Builder is disabled, click Anypoint Code Builder to add the icon to the Activity Bar.
-
If Anypoint Code Builder is not present, see Check for Anypoint Extension Pack Installation. If the Anypoint Extension Pack is installed, Check for Restricted Mode.
-
If your project or workspace is in restricted mode, the MuleSoft icon does not appear in the Activity Bar.
To determine whether your project or workspace is trusted or in restricted mode:
partial$acb-reusable-steps.adoc . Provide the following command to launch the Workspace Trust tab:
+
Workspace: Manage Workspace Trust+ If the Workspace Trust tab says You are in Restricted Mode, you can click Trust or Trust Parent.
+
. After trusting, check for the MuleSoft icon in the Activity Bar.
For more information about trust settings in the IDE, see Trusting a workspace in the VS Code documentation.
If a flow lacks a component or contains only a trigger, such as an HTTP Listener operation or the Scheduler, an error similar to the following appears in the Problems panel and from the configuration XML:
The content of element 'flow' is not complete. One of
'{"http://www.mulesoft.org/schema/mule/core":abstract-message-processor,
"http://www.mulesoft.org/schema/mule/core":abstract-mixed-content-message-processor}'
is expected.(cvc-complex-type.2.4.b)
To address this issue, add processing components or connector operations to your flow, such as a Logger or HTTP Request operation. partial$acb-component-info.adoc
This error can also occur if XML tags in the configuration file are corrupted or not properly closed. If you’ve already added components and the error persists, check the configuration XML for unclosed tags. To prevent XML corruption, save your work frequently and use source control management (SCM) to back up your projects.