[
https://issues.apache.org/jira/browse/CAMEL-20557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827046#comment-17827046
]
Claus Ibsen commented on CAMEL-20557:
-------------------------------------
TODO: openapi into rest-dsl model
TODO: api for creating consumer (impl in platform-http-vertx)
TODO: operationId -> direct:operationId mapping (spi for plugin custom
implementations)
TODO: option to return 204 for not yet implemented routes (so wont fail on
startup)
TODO: binding mode (and possible to override per operation so they have
different bindings)
TODO: documentation
TODO: example
TODO: api-context-path to return the schema file as-is (change host url)
> camel-rest - Add openapi to rest-dsl so you can expose rest services from
> existing schema
> -----------------------------------------------------------------------------------------
>
> Key: CAMEL-20557
> URL: https://issues.apache.org/jira/browse/CAMEL-20557
> Project: Camel
> Issue Type: New Feature
> Components: camel-core, rest
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 4.5.0
>
>
> rest()
> .openapi("my-schema.json")
> When you want to do contract-first with existing schema, then it would be
> good to make that first-class with rest-dsl, so the schema can be used as-is,
> and let it automatic map to direct:operationId routes like the convention is
> typically.
> The openapi should have same binding mode as rest-dsl, so it can automatic
> map to pojo or back if using json/xml via jackson etc.
> And the api-context can then return the schema file as-is (it may need to
> adjust the server part to be the actual server - like normal rest-dsl can do).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
