You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by kl...@apache.org on 2023/05/11 14:40:37 UTC
[camel] branch main updated: Upgrade Camel 4 migration guide for change to public API in camel-openapi-java
This is an automated email from the ASF dual-hosted git repository.
klease pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new b9e0b7f99c6 Upgrade Camel 4 migration guide for change to public API in camel-openapi-java
b9e0b7f99c6 is described below
commit b9e0b7f99c6e16edc74082e99833d4a0dd249f2d
Author: klease <kl...@cegetel.net>
AuthorDate: Thu May 11 16:40:06 2023 +0200
Upgrade Camel 4 migration guide for change to public API in camel-openapi-java
---
docs/user-manual/modules/ROOT/pages/camel-4-migration-guide.adoc | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/docs/user-manual/modules/ROOT/pages/camel-4-migration-guide.adoc b/docs/user-manual/modules/ROOT/pages/camel-4-migration-guide.adoc
index ab47d1a2c58..66813d44372 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4-migration-guide.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4-migration-guide.adoc
@@ -252,6 +252,15 @@ Now the context-path is not in use, and the endpoint can be called with `http://
NOTE: The `platform-http-starter` can also be used with Rest DSL.
+== camel-openapi-java
+
+The `camel-openapi-java` component has been changed to use `io.swagger.v3` libraries instead of `io.apicurio.datamodels`.
+As a result, the return type of the public method org.apache.camel.openapi.RestOpenApiReader.read() is now `io.swagger.v3.oas.models.OpenAPI` instead of `io.apicurio.datamodels.openapi.models.OasDocument`.
+When an OpenAPI 2.0 (swagger) specification is parsed, it is automatically upgraded to OpenAPI 3.0.x by the swagger parser.
+This version also supports OpenAPI 3.1.x specifications.
+The related spring-boot starter components have been modified to use the new return type.
+
+
== camel-optaplanner
The `camel-optaplanner` component has been change to use `SolverManager`. If you were using `SoverManager` in Camel 3, you don't need anymore the boolean useSolverManager in the Route.