Hi Bas,
I'm working on the fixes Claus mentioned and will commit a PR soon which
will remove the context path from the api paths.
But this has some side effects on the related camel-springboot starter
components which I also need to address.
Are you using camel-springdoc-starter or camel-openapi-java-starter, or
directly using the camel-openapi-java component in your springboot
application?
If you're using one of the camel springboot starters, I'm curious how
you've specified the context-path property in your application because
those starters are not currently using the server URL generated by the
Camel openapi-java component.
Thanks,
Karen Lease
On 19/01/2022 14:49, Claus Ibsen wrote:
Hi
There are some JIRAs and fixes on the way, so try 3.14.1 when its
released, or 3.15.0, or try the SNAPSHOT builds and help test.
On Wed, Jan 19, 2022 at 1:48 PM Bas Vanmeulebrouk <b...@civity.nl> wrote:
Dear list,
We have got a Spring Boot application which uses a Camel servlet running on a
specific context path. Camel-open-api-java is used to generate the OpenAPI
documentation for our API. We are upgrading this application from Camel 3.11.5
to 3.14.0. As described in the migration guide
(https://camel.apache.org/manual/camel-3x-upgrade-guide-3_13.html#_camel_openapi_java_camel_swagger_java),
the context path is now being added to the base path for all API calls. Since
this context path is added to the list of server URL's as well, tools to
generate client code based on our OpenAPI document try to access our API via a
URL with a duplicated context path, for example
http://localhost:8080/my-context-path/my-context-path/api/do-something. Any
ideas what we are missing? Is there an option to prevent this from happening?
Kind regards,
Bas Vanmeulebrouk,
Civity,
Handelsweg 6,
3707 NH Zeist,
the Netherlands,
www.civity.nl,
b...@civity.nl.
