docs: update for Spring Boot 4 and Jackson 3 migration

luisgomez29 · luisgomez29 · commit e600fb9264fc · 2025-12-11T11:40:52.000-05:00
diff --git a/async/cloudevents-json-jackson/README.md b/async/cloudevents-json-jackson/README.md
@@ -0,0 +1,10 @@
+# CloudEvents JSON Jackson Module
+
+This module was obtained from the official CloudEvents SDK Java repository at [https://github.com/cloudevents/sdk-java/blob/main/formats/json-jackson/](https://github.com/cloudevents/sdk-java/blob/main/formats/json-jackson/).
+
+## Changes from Original
+
+- Support limited to CloudEvents specification version 1.0
+- Updated dependencies from Jackson 2.x to Jackson 3.x
+- Adapted for compatibility with the reactive-commons-java project
+
diff --git a/docs/docs/migration-guides.md b/docs/docs/migration-guides.md
@@ -4,6 +4,45 @@ sidebar_position: 4
 
 # Migration
 
+## From 6.x.x to 7.x.x
+
+### Change notes
+
+- Upgrade to Spring Boot 4 and Jackson 3.
+
+### Actions
+
+#### 1. Update Jackson imports
+
+If you have custom code using Jackson, update the imports from `com.fasterxml.jackson.*` to `tools.jackson.*`.
+
+**Before (Jackson 2):**
+
+```java
+import com.fasterxml.jackson.databind.ObjectMapper;
+import com.fasterxml.jackson.databind.JsonNode;
+import com.fasterxml.jackson.core.type.TypeReference;
+```
+
+**After (Jackson 3):**
+
+```java
+import tools.jackson.databind.ObjectMapper;
+import tools.jackson.databind.JsonNode;
+import tools.jackson.core.type.TypeReference;
+```
+
+#### 2. Remove CloudEvents Jackson dependency
+
+If you were using CloudEvents, **remove** the `cloudevents-json-jackson` dependency as it only supports Jackson 2. A built-in module now provides Jackson 3 support for CloudEvents.
+
+```groovy
+// Remove this dependency
+implementation 'io.cloudevents:cloudevents-json-jackson:<version>'
+```
+
+---
+
 ## From 5.x.x to 6.x.x
 
 ### New features
@@ -32,17 +71,22 @@ public ConnectionFactoryCustomizer connectionFactoryCustomizer() {
 
 ### Actions
 
-- If your application uses the ReqReply pattern, you must explicitly set `app.async.app.listenReplies` to `true`.
-  Otherwise, it should be `false` to avoid unnecessary resource usage:
+#### 1. Configure listenReplies property
+
+If your application uses the ReqReply pattern, you must explicitly set `app.async.app.listenReplies` to `true`. Otherwise, it should be `false` to avoid unnecessary resource usage.
 
-```yaml title="application.yaml"
+**YAML Configuration:**
+
+```yaml
 app:
   async:
     app:
       listenReplies: true # set to true if ReqReply is required, false if not
 ```
 
-```java title="Programmatic configuration"
+**Programmatic Configuration:**
+
+```java
 @Configuration
 public class MyDomainConfig {
 
@@ -61,18 +105,22 @@ public class MyDomainConfig {
 }
 ```
 
----
+#### 2. Define the app domain
 
-- The domain `app` must be defined in your configuration. Otherwise, the application will throw an exception at startup:
+The domain `app` must be defined in your configuration. Otherwise, the application will throw an exception at startup.
 
-```yaml title="application.yaml"
+**YAML Configuration:**
+
+```yaml
 app:
   async:
     app: # Configure the 'app' domain
     # domain configuration goes here
 ```
 
-```java title="Programmatic configuration"
+**Programmatic Configuration:**
+
+```java
 @Configuration
 public class MyDomainConfig {
 
@@ -90,6 +138,8 @@ public class MyDomainConfig {
 }
 ```
 
+---
+
 ## From 4.x.x to 5.x.x
 
 ### New features
@@ -107,21 +157,23 @@ public class MyDomainConfig {
 
 ### Actions
 
-- The `app` domain needs to be defined to specify the configuration properties.
+#### 1. Update domain configuration structure
+
+The `app` domain needs to be defined to specify the configuration properties.
 
-Before:
+**Before:**
 
-```yaml title="application.yaml"
+```yaml
 app:
   async:
     withDLQRetry: true
     maxRetries: 1
     retryDelay: 1000
 ```
 
-Now:
+**After:**
 
-```yaml title="application.yaml"
+```yaml
 app:
   async:
     app: # this is the name of the default domain
@@ -130,9 +182,11 @@ app:
       retryDelay: 1000
 ```
 
-- Migrate the connection configuration:
+#### 2. Migrate connection configuration
 
-Before: the connection was defined manually in a Java class, as shown below:
+**Before:**
+
+The connection was defined manually in a Java class:
 
 ```java
 @Log4j2
@@ -171,9 +225,11 @@ public class MyDomainConfig {
 }
 ```
 
-Now: the connection is configured directly in the `application.yaml` file per domain:
+**After:**
+
+The connection is configured directly in the `application.yaml` file per domain:
 
-```yaml title="application.yaml"
+```yaml
 app:
   async:
     app: # this is the name of the default domain
@@ -193,9 +249,11 @@ app:
         virtual-host: /accounts
 ```
 
+**Alternative - Programmatic Configuration:**
+
 Domains can also be configured programmatically:
 
-```java title="Programmatic configuration"
+```java
 @Configuration
 public class MyDomainConfig {
 
diff --git a/docs/docs/reactive-commons/1-getting-started.md b/docs/docs/reactive-commons/1-getting-started.md
@@ -15,7 +15,7 @@ Commons.
 
 ## Requirements
 
-You need Java JRE installed (Java 17 or later).
+You need Java JRE installed (Java 17 or later) and Spring Boot 4.
 
 You also need to install RabbitMQ. Follow the [instructions from the website](https://www.rabbitmq.com/download.html).
 
@@ -54,7 +54,7 @@ dependencies {
 If you will use Cloud Events, you should include the Cloud Events dependency:
 ```groovy
 dependencies {
-    implementation 'io.cloudevents:cloudevents-json-jackson:4.0.1'
+    implementation 'io.cloudevents:cloudevents-core:4.0.1'
 }
 ```
 :::
@@ -139,7 +139,7 @@ Commons.
 
 ## Requirements
 
-You need Java JRE installed (Java 17 or later).
+You need Java JRE installed (Java 17 or later) and Spring Boot 4.
 
 ## Start Kafka
 
@@ -224,8 +224,7 @@ dependencies {
 If you will use Cloud Events, you should include the Cloud Events dependency:
 ```groovy
 dependencies {
-    implementation 'io.cloudevents:cloudevents-json-jackson:4.0.1'
-}
+    implementation 'io.cloudevents:cloudevents-core:4.0.1'
 ```
 :::
 
diff --git a/docs/docs/reactive-commons/10-wildcards.md b/docs/docs/reactive-commons/10-wildcards.md
@@ -37,7 +37,7 @@ example:
 ```java
 
 @Component
-@AllArgsConstructor
+@RequiredArgsConstructor
 public class DynamicSubscriber {
     private final DynamicRegistry registry;
 
diff --git a/docs/docs/reactive-commons/11-creating-a-cloud-event.md b/docs/docs/reactive-commons/11-creating-a-cloud-event.md
@@ -16,8 +16,6 @@ In order to instantiate a CloudEvent you may need to include the dependencies:
 
 ```groovy
 implementation 'io.cloudevents:cloudevents-core:<version>'
-// or
-implementation 'io.cloudevents:cloudevents-json-jackson:<version>'
 ```
 
 ## Creating a CloudEvent instance with our Data wrapper
@@ -65,7 +63,7 @@ add this classes:
 import io.cloudevents.core.builder.CloudEventBuilder;
 import io.cloudevents.CloudEvent;
 import io.cloudevents.jackson.JsonCloudEventData;
-import com.fasterxml.jackson.databind.ObjectMapper;
+import tools.jackson.databind.ObjectMapper;
 ```
 
 ```java
diff --git a/docs/docs/reactive-commons/configuration_properties/1-rabbitmq.md b/docs/docs/reactive-commons/configuration_properties/1-rabbitmq.md
@@ -443,9 +443,6 @@ Therefore, it is recommended to verify or create the queue beforehand to ensure
 ```java
 package sample;
 
-import com.fasterxml.jackson.core.type.TypeReference;
-import com.fasterxml.jackson.databind.JsonNode;
-import com.fasterxml.jackson.databind.ObjectMapper;
 import org.reactivecommons.api.domain.Command;
 import org.reactivecommons.async.api.DirectAsyncGateway;
 import org.reactivecommons.async.impl.config.annotations.EnableDirectAsyncGateway;
@@ -456,6 +453,9 @@ import org.springframework.stereotype.Component;
 import reactor.core.publisher.Mono;
 import reactor.rabbitmq.OutboundMessage;
 import reactor.rabbitmq.OutboundMessageResult;
+import tools.jackson.core.type.TypeReference;
+import tools.jackson.databind.JsonNode;
+import tools.jackson.databind.ObjectMapper;
 
 @Component
 @EnableDirectAsyncGateway
diff --git a/docs/package-lock.json b/docs/package-lock.json
diff --git a/docs/package.json b/docs/package.json
