[
https://issues.apache.org/jira/browse/CAMEL-9425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Posta closed CAMEL-9425.
----------------------------------
Thx [~davsclaus], repeating the servlet config solved it
> base.path, host, and schemes are all ignored for generating the swagger
> definitions
> -----------------------------------------------------------------------------------
>
> Key: CAMEL-9425
> URL: https://issues.apache.org/jira/browse/CAMEL-9425
> Project: Camel
> Issue Type: Bug
> Components: camel-swagger
> Affects Versions: 2.16.1
> Reporter: Christian Posta
> Assignee: Claus Ibsen
>
> *This affects camel-swagger-java*
> How do we add that component to the list?
> For example, i am using camel-servlet to serve APIs at path "foo"...
> i then have rest().get("/hello")......
> for the restConfiguration() I have
> {code}
> restConfiguration().component("servlet").bindingMode(RestBindingMode.json)
> .apiContextPath("/api-doc")
> .apiProperty("api.title", "User API")
> .apiProperty("api.version", "1.2.3")
> .apiProperty("api.description", "REST API for controlling the
> jobs")
> .apiProperty("cors", "true")
> .apiProperty("base.path", "/camel")
> .apiProperty("schemas", "http")
> .apiProperty("host", "postamac.local")
> {code}
> but when I hit /came/api-docs, the rest endpoints all omit the "/camel" base
> context path.
> what's the expected behavior here? I assumed that the schemes+host+base.path
> would allow me to override the base path. is this not the right assumption?
> BTW... the prop name is "schemas" when it should be "schemes" ... we should
> change this to as expected, how do we do that in terms of backward
> compatibility? i can open another jira for that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
