W-19449965-Mule-410-dm

antora.yml

@@ -1,6 +1,6 @@
 name: mule-runtime
 title: Mule Runtime
 version: '4.9'
-display_version: '4.9'
+display_version: '4.10'
 nav:
 - modules/ROOT/nav.adoc

modules/ROOT/nav.adoc

@@ -49,6 +49,7 @@ include::partial$nav-app-dev.adoc[]
   *** xref:creating-and-managing-a-cluster-manually.adoc[Create and Manage a Cluster Manually]
   *** xref:hadr-guide.adoc[High Availability and Disaster Recovery]
 * xref:mule-upgrade-tool.adoc[Mule Upgrade Tool]
+* xref:mule-troubleshooting-plugin.adoc[Mule Troubleshooting Plugin]
 * xref:using-maven-with-mule.adoc[Maven Support in Mule]
  ** xref:mmp-concept.adoc[Mule Maven Plugin]
  ** xref:package-a-mule-application.adoc[Package a Mule Application]

modules/ROOT/pages/_partials/mmp-deploy-to-rtf.adoc

@@ -17,7 +17,7 @@ If you want to deploy applications to Runtime Fabric using a different method, s
 
 * Ensure that the Mule Maven Plugin is added to your project
 +
-See xref:mmp-concept.adoc#add-mmp[Add the Mule Maven Plugin to a Mule Project] for instructions.
+See xref:mule-runtime::mmp-concept.adoc#add-mmp[Add the Mule Maven Plugin to a Mule Project] for instructions.
 * You understand and have available the number of resources required to deploy to Runtime Fabric +
 See xref:runtime-fabric::deploy-resource-allocation-self-managed.adoc[]for more information.
 * The application is already published in Exchange +
@@ -30,7 +30,7 @@ See xref:exchange::to-publish-assets-maven.adoc[Publish and Deploy Exchange Asse
 
 * Ensure that the Mule Maven Plugin is added to your project
 +
-See <<add-mmp, Add the Mule Maven Plugin to a Mule Project>> for instructions.
+See xref:mule-runtime::mmp-concept.adoc#add-mmp[Add the Mule Maven Plugin to a Mule Project] for instructions.
 * You understand and have available the number of resources required to deploy to Runtime Fabric +
 See xref:runtime-fabric::deploy-resource-allocation-self-managed.adoc[Resource Allocation on Anypoint Runtime Fabric] for more information.
 * The application is already published in Exchange +

modules/ROOT/pages/_partials/upgrade-tool.adoc

@@ -1,5 +1,5 @@
 //This content is reused in:
-//mule-upgrade-tool.adoc
+//mule-upgrade-tool.adoc under the Before You Begin section and  Upgrading Clustered Mule Instances section.
 
 // Before You Begin
 // tag::BeforeYouBegin[]
@@ -18,6 +18,9 @@ Download Mule runtime distributions from the https://help.mulesoft.com/s/[Help C
 * At least 2 GB of available disk space on the file system and access privileges to install the new Mule distribution.
 * (For Windows environments) The execution policy for Powershell scripts set to *Unrestricted*.
 * If Anypoint Monitoring agent is installed, uninstall it prior to the upgrade.
+* Rename the `$MULE_HOME` directory before running the upgrade tool to use a generic name or one that matches the target version. For example, `mule-enterprise-4.9.8`. 
++
+Renaming the directory after running the upgrade tool causes Anypoint Monitoring to stop working. To restore Anypoint Monitoring, uninstall and reinstall it. Alternatively, you can leave the directory name unchanged.
 // end::BeforeYouBegin[]
 
 // Upgrade Or Update Mule

modules/ROOT/pages/feature-flagging.adoc

@@ -93,10 +93,6 @@ The following table shows the available feature flags, a description of their fu
 
 * 4.5.0
 
-* 4.4.1
-
-* 4.3.1
-
 *Issue ID*
 
 * MULE-19919
@@ -201,8 +197,6 @@ The following table shows the available feature flags, a description of their fu
 
 *Enabled by Default Since*
 
-* 4.4.0
-
 * 4.3.0
 
 *Issue ID*
@@ -249,9 +243,9 @@ The following table shows the available feature flags, a description of their fu
 
 * 4.5.0
 
-* 4.4.0-20220221
+* 4.4.0-20220124
 
-* 4.3.0-20220221
+* 4.3.0-20220124
 
 *Enabled by Default Since*
 
@@ -333,11 +327,11 @@ Suppressed errors are treated as underlying causes that can also be matched by O
 
 *Available Since*
 
-* 4.4.0-20211227
+* 4.5.0
 
 *Enabled by Default Since*
 
-* Not enabled by default in any Mule version.
+* 4.5.0
 
 *Issue ID*
 
@@ -386,7 +380,7 @@ Suppressed errors are treated as underlying causes that can also be matched by O
 *Issue ID*
 
 * W-11071481
-<.^|`ENFORCE_ERROR_TYPES_VALIDATION` 
+<.^|`ENFORCE_ERROR_TYPES_VALIDATION`
 |When enabled, error types validations are enforced, even for error handlers/components that aren't being referenced.
 This feature isn't configurable by system property.
 
@@ -529,9 +523,7 @@ This feature isn't configurable by system property.
 
 *Enabled by Default Since*
 
-* 4.5.0
-* 4.4.0-202210
-* 4.3.0-202210
+* Enabled by default in any Mule version
 
 *Issue ID*
 
@@ -573,17 +565,7 @@ This feature isn't configurable by system property.
 
 *Enabled by Default Since*
 
-* 4.5.0
-
-* 4.4.0
-
-* 4.3.0
-
-* 4.2.0
-
-* 4.1.0
-
-* 4.0.0
+* Enabled by default in any Mule version
 
 *Issue ID*
 
@@ -614,7 +596,7 @@ This feature isn't configurable by system property.
 
 *Enabled by Default Since*
 
-* 4.5.0
+* Not enabled by default in any Mule version
 
 *Issue ID*
 
@@ -772,17 +754,50 @@ This feature isn't configurable by system property.
 
 *Available Since*
 
+* 4.10.0
 * 4.9.2
 * 4.6.14
 * 4.4.0-20250217
 
 *Enabled by Default Since*
 
-* Not enabled by default in any Mule version
+* 4.10.0
 
 *Issue ID*
 
 * W-16941297
+<.^|`mule.repeatableStreaming.bytes.eagerRead`
+|When enabled, the `read` methods of bytes repeatable streams return immediately with any available data. If disabled, they don't return until the requested `len` is fully read. Set this property to `true` to process SSE events over HTTP as they arrive instead of buffering them.
+
+*Available Since*
+
+* 4.10.0
+* 4.9.7
+* 4.6.20
+* 4.4.1
+
+*Enabled by Default Since*
+
+* Not enabled by default in any Mule version
+
+*Issue ID*
+
+* W-18716253
+<.^|`mule.disable.optimised.notification.handler.dynamic.resolution.update.based.on.delegate`
+|When disabled, dynamic resolution of notification handling doesn't occur after the Mule artifact is initialized. This can cause race conditions that affect monitoring metrics.
+
+*Available Since*
+
+* 4.10.0
+
+*Enabled by Default Since*
+
+* Not enabled by default in any Mule version
+
+*Issue ID*
+
+* W-16828516
+
 |===
 
 == See Also

modules/ROOT/pages/migration-mel.adoc

@@ -417,10 +417,10 @@ can be used instead. The next example shows how a regex is used in DataWeave to
 
 == See Also
 
-xref:dataweave.adoc[DataWeave Language]
-
-https://blogs.mulesoft.com/dev/mule-dev/why-dataweave-main-expression-language-mule-4/[Why DataWeave is the Main Expression Language in Mule 4 Beta]
+* xref:dataweave.adoc[DataWeave Language]
+* https://blogs.mulesoft.com/dev/mule-dev/why-dataweave-main-expression-language-mule-4/[Why DataWeave is the Main Expression Language in Mule 4 Beta]
 
+////
 * MEL expressions to DataWeave 2.x (2.1?)
 * Preliminary plan is to take examples from Mule 3 docs and show how to migrate them to 4.0. See https://docs.mulesoft.com/mule-user-guide/v/3.9/mule-expression-language-mel
 * 3 primary use cases (from Dan Feist):
@@ -482,9 +482,7 @@ FROM ANA'S BLOG:
 == Date Time
 * MEL: `#[payload.name ++ '.' ++ dataType.mimeType.subType]`
 * DataWeave: `#[payload ++ { date : now() }]`
-////
 
-////
   Note:
   Mariano G. says most people using MEL to access the payload. For simple expressions, migration tool will do it, but we will have to help migrate complex mappings. No date on migrator, but is first priority after GA. Somewhere in the Mule.