Croway opened a new pull request, #217:
URL: https://github.com/apache/camel-spring-boot-examples/pull/217

   Related: [CAMEL-22857](https://issues.apache.org/jira/browse/CAMEL-22857) 
(Add support for Jackson 3)
   
   ## Summary
   
   Spring Boot 4 uses Jackson 3 by default, and most JSON examples already use 
`camel-jackson3-starter`. `docling` and `vault` were the last two examples on 
the Jackson 2 data format (`camel-jackson-starter`). This PR moves them to 
`camel-jackson3-starter`. Their routes need no change, because both lines 
register the same `jackson` data format name.
   
   The other examples were checked against the Jackson 2 → 3 migration rules 
(with `dependency:tree` on every module, plus a source search for Jackson 
imports, `onException` clauses, mapper beans and `camel.dataformat.jackson.*` / 
`spring.jackson.*` properties). Nothing else needs to change:
   - `ai-agent` gets `camel-jackson` through `camel-jq-starter`. It only uses 
`jq` expressions, which need Jackson 2, and no JSON data format.
   - `twitter-salesforce` only uses `com.fasterxml.jackson.annotation`, which 
is shared by both Jackson lines.
   
   ## Verification
   
   Each example was run per its README (Vault + Postgres, docling-serve in 
containers), first on Jackson 2 and then on Jackson 3:
   
   | Example | Jackson 2 | Jackson 3 |
   |---|---|---|
   | `vault` | `[{"brand":"Ford","model":"Mustang","year":2024}]` | identical |
   | `docling` (Markdown) | output | identical |
   | `docling` (metadata JSON) | 
`{"schema_name":"DoclingDocument","version":…}` | Same content and size, 
properties in alphabetical order (`{"body":…,"furniture":…}`), the Jackson 3 
default `SORT_PROPERTIES_ALPHABETICALLY` |
   
   `./mvnw -pl vault,docling clean install` passes. Neither example has tests.
   
   _Claude Code on behalf of Federico Mariani_
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to