[jira] [Updated] (CAMEL-20625) Create a camel-google-pubsub-lite component
[ https://issues.apache.org/jira/browse/CAMEL-20625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20625: Fix Version/s: 4.6.0 > Create a camel-google-pubsub-lite component > --- > > Key: CAMEL-20625 > URL: https://issues.apache.org/jira/browse/CAMEL-20625 > Project: Camel > Issue Type: New Feature > Components: camel-google >Reporter: Stanislav Deviatov >Priority: Minor > Fix For: 4.6.0 > > > The [Pub/Sub > connector|https://camel.apache.org/components/4.4.x/google-pubsub-component.html] > isn't compatible with Pub/Sub Lite service due to API and message model > differences. This new connector will: > * Enable seamless Pub/Sub Lite integration with Apache Camel routes. > * Leverage Camel's capabilities for message processing and cost-effective > Pub/Sub Lite usage. > The following link provides information on the differences between Pub/Sub > and Pub/Sub Lite. Check it out: > * [https://cloud.google.com/pubsub/docs/overview#lite] > * [https://cloud.google.com/pubsub/docs/choosing-pubsub-or-lite] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20624) camel-http - OAuth2 support adds duplicate Authorization header if one already exists on the Exchange
[
https://issues.apache.org/jira/browse/CAMEL-20624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17831647#comment-17831647
]
Claus Ibsen commented on CAMEL-20624:
-
Thanks for reporting and the PR
> camel-http - OAuth2 support adds duplicate Authorization header if one
> already exists on the Exchange
> -
>
> Key: CAMEL-20624
> URL: https://issues.apache.org/jira/browse/CAMEL-20624
> Project: Camel
> Issue Type: Bug
> Components: camel-http
>Affects Versions: 4.4.1
>Reporter: Joshua Grisham
>Priority: Minor
> Fix For: 4.4.2, 4.6.0
>
>
> If the Exchange already has a header with the name "Authorization" and the
> OAuth2 feature of camel-http is used, the existing Authorization header is
> left on the request to the target and a second header with the same name is
> added.
> This very often results in a denied HTTP request (e.g. HTTP 400 Bad Request)
> as well as conflicts with RFC 7230/7235 for example here: [RFC 7230:
> Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
> (rfc-editor.org)|https://www.rfc-editor.org/rfc/rfc7230#section-3.2.2]
> {panel:title=3.2.2. Field Order}
> ...
> A sender MUST NOT generate multiple header fields with the same field name in
> a message unless either the entire field value for that header field is
> defined as a comma-separated list [i.e., #(values)|#(values)] or the header
> field is a well-known exception (as noted below).
> ...
> {panel}
>
> A proposed fix to this is to update the existing header if it already exists
> instead of always adding a new header (e.g. `request.setHeader()` instead of
> `request.addHeader()`)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20624) camel-http - OAuth2 support adds duplicate Authorization header if one already exists on the Exchange
[
https://issues.apache.org/jira/browse/CAMEL-20624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20624.
-
Resolution: Fixed
> camel-http - OAuth2 support adds duplicate Authorization header if one
> already exists on the Exchange
> -
>
> Key: CAMEL-20624
> URL: https://issues.apache.org/jira/browse/CAMEL-20624
> Project: Camel
> Issue Type: Bug
> Components: camel-http
>Affects Versions: 4.4.1
>Reporter: Joshua Grisham
>Priority: Minor
> Fix For: 4.4.2, 4.6.0
>
>
> If the Exchange already has a header with the name "Authorization" and the
> OAuth2 feature of camel-http is used, the existing Authorization header is
> left on the request to the target and a second header with the same name is
> added.
> This very often results in a denied HTTP request (e.g. HTTP 400 Bad Request)
> as well as conflicts with RFC 7230/7235 for example here: [RFC 7230:
> Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
> (rfc-editor.org)|https://www.rfc-editor.org/rfc/rfc7230#section-3.2.2]
> {panel:title=3.2.2. Field Order}
> ...
> A sender MUST NOT generate multiple header fields with the same field name in
> a message unless either the entire field value for that header field is
> defined as a comma-separated list [i.e., #(values)|#(values)] or the header
> field is a well-known exception (as noted below).
> ...
> {panel}
>
> A proposed fix to this is to update the existing header if it already exists
> instead of always adding a new header (e.g. `request.setHeader()` instead of
> `request.addHeader()`)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20493) camel-core: concurrency issue copying headers
[ https://issues.apache.org/jira/browse/CAMEL-20493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17831646#comment-17831646 ] Claus Ibsen commented on CAMEL-20493: - Merged PR so lets see if we have those test errors again. > camel-core: concurrency issue copying headers > - > > Key: CAMEL-20493 > URL: https://issues.apache.org/jira/browse/CAMEL-20493 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 4.4.0, 4.5.0 >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.x > > Attachments: concurrency-issue.txt > > > It looks like under some rare circumstances the copy of message headers can > suffer from concurrency issues. > Please look at the attached log, extracted from an execution of the test > JmsProducerConcurrentWithReplyTest. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20493) camel-core: concurrency issue copying headers
[ https://issues.apache.org/jira/browse/CAMEL-20493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17831644#comment-17831644 ] Claus Ibsen commented on CAMEL-20493: - https://github.com/apache/camel/pull/13598 > camel-core: concurrency issue copying headers > - > > Key: CAMEL-20493 > URL: https://issues.apache.org/jira/browse/CAMEL-20493 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 4.4.0, 4.5.0 >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.x > > Attachments: concurrency-issue.txt > > > It looks like under some rare circumstances the copy of message headers can > suffer from concurrency issues. > Please look at the attached log, extracted from an execution of the test > JmsProducerConcurrentWithReplyTest. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20571) camel-infinispan: Upgrade to 15.x
[ https://issues.apache.org/jira/browse/CAMEL-20571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20571. - Resolution: Fixed okay fixed SB > camel-infinispan: Upgrade to 15.x > - > > Key: CAMEL-20571 > URL: https://issues.apache.org/jira/browse/CAMEL-20571 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-infinispan >Reporter: James Netherton >Assignee: James Netherton >Priority: Major > Fix For: 4.6.0 > > > Infinispan 15 is now available: > https://infinispan.org/blog/2024/03/13/infinispan-15 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (CAMEL-20571) camel-infinispan: Upgrade to 15.x
[ https://issues.apache.org/jira/browse/CAMEL-20571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reopened CAMEL-20571: - > camel-infinispan: Upgrade to 15.x > - > > Key: CAMEL-20571 > URL: https://issues.apache.org/jira/browse/CAMEL-20571 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-infinispan >Reporter: James Netherton >Assignee: James Netherton >Priority: Major > Fix For: 4.6.0 > > > Infinispan 15 is now available: > https://infinispan.org/blog/2024/03/13/infinispan-15 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20571) camel-infinispan: Upgrade to 15.x
[ https://issues.apache.org/jira/browse/CAMEL-20571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17831642#comment-17831642 ] Claus Ibsen commented on CAMEL-20571: - This broke camel-spring-boot [ERROR] Failed to execute goal on project camel-infinispan-starter: Could not resolve dependencies for project org.apache.camel.springboot:camel-infinispan-starter:jar:4.5.0-SNAPSHOT: The following artifacts could not be resolved: org.infinispan:infinispan-core-jakarta:jar:15.0.0.Final (absent), org.infinispan:infinispan-spring5-remote:jar:15.0.0.Final (absent), org.infinispan:proto-sample-domain-definition:jar:15.0.0.Final (absent): Could not find artifact org.infinispan:infinispan-core-jakarta:jar:15.0.0.Final in central (https://repo.maven.apache.org/maven2) > camel-infinispan: Upgrade to 15.x > - > > Key: CAMEL-20571 > URL: https://issues.apache.org/jira/browse/CAMEL-20571 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-infinispan >Reporter: James Netherton >Assignee: James Netherton >Priority: Major > Fix For: 4.6.0 > > > Infinispan 15 is now available: > https://infinispan.org/blog/2024/03/13/infinispan-15 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20626) deprecate experimental DSLs
Claus Ibsen created CAMEL-20626: --- Summary: deprecate experimental DSLs Key: CAMEL-20626 URL: https://issues.apache.org/jira/browse/CAMEL-20626 Project: Camel Issue Type: Task Reporter: Claus Ibsen Fix For: 4.6.0 camel-js-dsl and camel-jsh-dsl. They were some very basic prototypes. You can use javascript with camel with the camel-javascript component. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20557) camel-rest - Add openapi to rest-dsl so you can expose rest services from existing schema
[
https://issues.apache.org/jira/browse/CAMEL-20557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17831471#comment-17831471
]
Claus Ibsen commented on CAMEL-20557:
-
TODO: binding advice before|after calling the direct route (dynamic adapted to
the API operation)
> 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.6.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)
[jira] [Comment Edited] (CAMEL-20557) camel-rest - Add openapi to rest-dsl so you can expose rest services from existing schema
[
https://issues.apache.org/jira/browse/CAMEL-20557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827046#comment-17827046
]
Claus Ibsen edited comment on CAMEL-20557 at 3/27/24 4:43 PM:
--
TODO: openapi into rest-dsl model *DONE*
TODO: configure some special new options in rest-dsl for openapi *DONE*
TODO: camel-rest-openapi add consumer *DONE*
TODO: api for creating consumer (impl in platform-http-vertx) *DONE*
TODO: operationId -> direct:operationId mapping (spi for plugin custom
implementations) *DONE*
TODO: option to return 204 for not yet implemented routes (so wont fail on
startup) *DONE*
TODO: option to validate all apis have route mapping (so can report which apis
that are missing) *DONE*
TODO: binding mode (and possible to override per operation so they have
different bindings)
TODO: request validation on|off *DONE*
TODO: documentation *DONE*
TODO: example *DONE*
TODO: api-context-path to return the schema file as-is *DONE*
TODO: rest-openapi - specifciationUri should be String type for better tooling
support *DONE*
TODO: mock mode to load sample data from classpath/file system *DONE*
TODO: rest registry / managed rest registry *WONT FIX*
TODO: http summary to show all operations *DONE*
was (Author: davsclaus):
TODO: openapi into rest-dsl model *DONE*
TODO: configure some special new options in rest-dsl for openapi *DONE*
TODO: camel-rest-openapi add consumer *DONE*
TODO: api for creating consumer (impl in platform-http-vertx) *DONE*
TODO: operationId -> direct:operationId mapping (spi for plugin custom
implementations) *DONE*
TODO: option to return 204 for not yet implemented routes (so wont fail on
startup) *DONE*
TODO: option to validate all apis have route mapping (so can report which apis
that are missing) *DONE*
TODO: binding mode (and possible to override per operation so they have
different bindings)
TODO: request validation on|off *DONE*
TODO: documentation
TODO: example *DONE*
TODO: api-context-path to return the schema file as-is *DONE*
TODO: rest-openapi - specifciationUri should be String type for better tooling
support *DONE*
TODO: mock mode to load sample data from classpath/file system *DONE*
TODO: rest registry / managed rest registry *WONT FIX*
TODO: http summary to show all operations *DONE*
> 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.6.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)
[jira] [Updated] (CAMEL-20624) camel-http - OAuth2 support adds duplicate Authorization header if one already exists on the Exchange
[
https://issues.apache.org/jira/browse/CAMEL-20624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20624:
Fix Version/s: 4.4.2
4.6.0
> camel-http - OAuth2 support adds duplicate Authorization header if one
> already exists on the Exchange
> -
>
> Key: CAMEL-20624
> URL: https://issues.apache.org/jira/browse/CAMEL-20624
> Project: Camel
> Issue Type: Bug
> Components: camel-http
>Affects Versions: 4.4.1
>Reporter: Joshua Grisham
>Priority: Minor
> Fix For: 4.4.2, 4.6.0
>
>
> If the Exchange already has a header with the name "Authorization" and the
> OAuth2 feature of camel-http is used, the existing Authorization header is
> left on the request to the target and a second header with the same name is
> added.
> This very often results in a denied HTTP request (e.g. HTTP 400 Bad Request)
> as well as conflicts with RFC 7230/7235 for example here: [RFC 7230:
> Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
> (rfc-editor.org)|https://www.rfc-editor.org/rfc/rfc7230#section-3.2.2]
> {panel:title=3.2.2. Field Order}
> ...
> A sender MUST NOT generate multiple header fields with the same field name in
> a message unless either the entire field value for that header field is
> defined as a comma-separated list [i.e., #(values)|#(values)] or the header
> field is a well-known exception (as noted below).
> ...
> {panel}
>
> A proposed fix to this is to update the existing header if it already exists
> instead of always adding a new header (e.g. `request.setHeader()` instead of
> `request.addHeader()`)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20625) Create a camel-google-pubsub-lite component
Stanislav Deviatov created CAMEL-20625: -- Summary: Create a camel-google-pubsub-lite component Key: CAMEL-20625 URL: https://issues.apache.org/jira/browse/CAMEL-20625 Project: Camel Issue Type: New Feature Components: camel-google Reporter: Stanislav Deviatov The [Pub/Sub connector|https://camel.apache.org/components/4.4.x/google-pubsub-component.html] isn't compatible with Pub/Sub Lite service due to API and message model differences. This new connector will: * Enable seamless Pub/Sub Lite integration with Apache Camel routes. * Leverage Camel's capabilities for message processing and cost-effective Pub/Sub Lite usage. The following link provides information on the differences between Pub/Sub and Pub/Sub Lite. Check it out: * [https://cloud.google.com/pubsub/docs/overview#lite] * [https://cloud.google.com/pubsub/docs/choosing-pubsub-or-lite] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20624) camel-http - OAuth2 support adds duplicate Authorization header if one already exists on the Exchange
Joshua Grisham created CAMEL-20624:
--
Summary: camel-http - OAuth2 support adds duplicate Authorization
header if one already exists on the Exchange
Key: CAMEL-20624
URL: https://issues.apache.org/jira/browse/CAMEL-20624
Project: Camel
Issue Type: Bug
Components: camel-http
Affects Versions: 4.4.1
Reporter: Joshua Grisham
If the Exchange already has a header with the name "Authorization" and the
OAuth2 feature of camel-http is used, the existing Authorization header is left
on the request to the target and a second header with the same name is added.
This very often results in a denied HTTP request (e.g. HTTP 400 Bad Request) as
well as conflicts with RFC 7230/7235 for example here: [RFC 7230: Hypertext
Transfer Protocol (HTTP/1.1): Message Syntax and Routing
(rfc-editor.org)|https://www.rfc-editor.org/rfc/rfc7230#section-3.2.2]
{panel:title=3.2.2. Field Order}
...
A sender MUST NOT generate multiple header fields with the same field name in a
message unless either the entire field value for that header field is defined
as a comma-separated list [i.e., #(values)|#(values)] or the header field is a
well-known exception (as noted below).
...
{panel}
A proposed fix to this is to update the existing header if it already exists
instead of always adding a new header (e.g. `request.setHeader()` instead of
`request.addHeader()`)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-20557) camel-rest - Add openapi to rest-dsl so you can expose rest services from existing schema
[
https://issues.apache.org/jira/browse/CAMEL-20557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827046#comment-17827046
]
Claus Ibsen edited comment on CAMEL-20557 at 3/27/24 1:51 PM:
--
TODO: openapi into rest-dsl model *DONE*
TODO: configure some special new options in rest-dsl for openapi *DONE*
TODO: camel-rest-openapi add consumer *DONE*
TODO: api for creating consumer (impl in platform-http-vertx) *DONE*
TODO: operationId -> direct:operationId mapping (spi for plugin custom
implementations) *DONE*
TODO: option to return 204 for not yet implemented routes (so wont fail on
startup) *DONE*
TODO: option to validate all apis have route mapping (so can report which apis
that are missing) *DONE*
TODO: binding mode (and possible to override per operation so they have
different bindings)
TODO: request validation on|off *DONE*
TODO: documentation
TODO: example *DONE*
TODO: api-context-path to return the schema file as-is *DONE*
TODO: rest-openapi - specifciationUri should be String type for better tooling
support *DONE*
TODO: mock mode to load sample data from classpath/file system *DONE*
TODO: rest registry / managed rest registry *WONT FIX*
TODO: http summary to show all operations *DONE*
was (Author: davsclaus):
TODO: openapi into rest-dsl model *DONE*
TODO: configure some special new options in rest-dsl for openapi *DONE*
TODO: camel-rest-openapi add consumer *DONE*
TODO: api for creating consumer (impl in platform-http-vertx) *DONE*
TODO: operationId -> direct:operationId mapping (spi for plugin custom
implementations) *DONE*
TODO: option to return 204 for not yet implemented routes (so wont fail on
startup) *DONE*
TODO: option to validate all apis have route mapping (so can report which apis
that are missing) *DONE*
TODO: binding mode (and possible to override per operation so they have
different bindings)
TODO: request validation on|off *DONE*
TODO: documentation
TODO: example *DONE*
TODO: api-context-path to return the schema file as-is *DONE*
TODO: rest-openapi - specifciationUri should be String type for better tooling
support *DONE*
TODO: mock mode to load sample data from classpath/file system *DONE*
TODO: rest registry / managed rest registry
TODO: http summary to show all operations *DONE*
> 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.6.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)
[jira] [Comment Edited] (CAMEL-20557) camel-rest - Add openapi to rest-dsl so you can expose rest services from existing schema
[
https://issues.apache.org/jira/browse/CAMEL-20557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827046#comment-17827046
]
Claus Ibsen edited comment on CAMEL-20557 at 3/27/24 1:46 PM:
--
TODO: openapi into rest-dsl model *DONE*
TODO: configure some special new options in rest-dsl for openapi *DONE*
TODO: camel-rest-openapi add consumer *DONE*
TODO: api for creating consumer (impl in platform-http-vertx) *DONE*
TODO: operationId -> direct:operationId mapping (spi for plugin custom
implementations) *DONE*
TODO: option to return 204 for not yet implemented routes (so wont fail on
startup) *DONE*
TODO: option to validate all apis have route mapping (so can report which apis
that are missing) *DONE*
TODO: binding mode (and possible to override per operation so they have
different bindings)
TODO: request validation on|off *DONE*
TODO: documentation
TODO: example *DONE*
TODO: api-context-path to return the schema file as-is *DONE*
TODO: rest-openapi - specifciationUri should be String type for better tooling
support *DONE*
TODO: mock mode to load sample data from classpath/file system *DONE*
TODO: rest registry / managed rest registry
TODO: http summary to show all operations *DONE*
was (Author: davsclaus):
TODO: openapi into rest-dsl model *DONE*
TODO: configure some special new options in rest-dsl for openapi *DONE*
TODO: camel-rest-openapi add consumer *DONE*
TODO: api for creating consumer (impl in platform-http-vertx) *DONE*
TODO: operationId -> direct:operationId mapping (spi for plugin custom
implementations) *DONE*
TODO: option to return 204 for not yet implemented routes (so wont fail on
startup) *DONE*
TODO: option to validate all apis have route mapping (so can report which apis
that are missing) *DONE*
TODO: binding mode (and possible to override per operation so they have
different bindings)
TODO: request validation on|off *DONE*
TODO: documentation
TODO: example *DONE*
TODO: api-context-path to return the schema file as-is (change host url)
TODO: rest-openapi - specifciationUri should be String type for better tooling
support *DONE*
TODO: mock mode to load sample data from classpath/file system *DONE*
TODO: rest registry / managed rest registry
TODO: http summary to show all operations *DONE*
> 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.6.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)
[jira] [Commented] (CAMEL-20623) camel-rest-openapi - Use another json validator that is jakartaee compatible
[ https://issues.apache.org/jira/browse/CAMEL-20623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17831355#comment-17831355 ] Claus Ibsen commented on CAMEL-20623: - It also seems its not open source. I cannot find the source code repo where its located for swagger-request-validator-core > camel-rest-openapi - Use another json validator that is jakartaee compatible > > > Key: CAMEL-20623 > URL: https://issues.apache.org/jira/browse/CAMEL-20623 > Project: Camel > Issue Type: Improvement > Components: camel-rest-openapi >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.6.0 > > > The library it uses from atlassian is cr** as it has some static classloader > hell, that uses old javax library, and you can't turn it off or configure it > differently. > java.lang.NoClassDefFoundError: javax/mail/internet/AddressException > at > com.github.fge.jsonschema.library.format.CommonFormatAttributesDictionary.(CommonFormatAttributesDictionary.java:56) > ~[json-schema-validator-2.2.14.jar:?] > at > com.github.fge.jsonschema.library.format.DraftV3FormatAttributesDictionary.(DraftV3FormatAttributesDictionary.java:47) > ~[json-schema-validator-2.2.14.jar:?] > at > com.github.fge.jsonschema.library.DraftV3Library.(DraftV3Library.java:36) > ~[json-schema-validator-2.2.14.jar:?] > at > com.github.fge.jsonschema.cfg.ValidationConfigurationBuilder.(ValidationConfigurationBuilder.java:63) > ~[json-schema-validator-2.2.14.jar:?] > at > com.github.fge.jsonschema.cfg.ValidationConfiguration.newBuilder(ValidationConfiguration.java:97) > ~[json-schema-validator-2.2.14.jar:?] > at > com.github.fge.jsonschema.cfg.ValidationConfiguration.byDefault(ValidationConfiguration.java:107) > ~[json-schema-validator-2.2.14.jar:?] > at > com.github.fge.jsonschema.main.JsonSchemaFactoryBuilder.(JsonSchemaFactoryBuilder.java:68) > ~[json-schema-validator-2.2.14.jar:?] > at > com.github.fge.jsonschema.main.JsonSchemaFactory.newBuilder(JsonSchemaFactory.java:123) > ~[json-schema-validator-2.2.14.jar:?] > at > com.atlassian.oai.validator.schema.SwaggerV20Library.schemaFactory(SwaggerV20Library.java:67) > ~[swagger-request-validator-core-2.40.0.jar:?] > at > com.atlassian.oai.validator.schema.SwaggerV20Library.schemaFactory(SwaggerV20Library.java:56) > ~[swagger-request-validator-core-2.40.0.jar:?] > at > com.atlassian.oai.validator.schema.SchemaValidator.(SchemaValidator.java:126) > ~[swagger-request-validator-core-2.40.0.jar:?] > at > com.atlassian.oai.validator.OpenApiInteractionValidator.(OpenApiInteractionValidator.java:161) > ~[swagger-request-validator-core-2.40.0.jar:?] > at > com.atlassian.oai.validator.OpenApiInteractionValidator.(OpenApiInteractionValidator.java:50) > ~[swagger-request-validator-core-2.40.0.jar:?] > at > com.atlassian.oai.validator.OpenApiInteractionValidator$Builder.build(OpenApiInteractionValidator.java:674) > ~[swagger-request-validator-core-2.40.0.jar:?] > at > org.apache.camel.component.rest.openapi.RestOpenApiEndpoint.configureRequestValidator(RestOpenApiEndpoint.java:822) > ~[camel-rest-openapi-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] > at > org.apache.camel.component.rest.openapi.RestOpenApiProcessor.process(RestOpenApiProcessor.java:101) > ~[camel-rest-openapi-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] > at > org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.process(DefaultAsyncProcessorAwaitManager.java:82) > ~[camel-base-engine-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] > at > org.apache.camel.support.AsyncProcessorSupport.process(AsyncProcessorSupport.java:32) > ~[camel-support-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] > at > org.apache.camel.component.platform.http.vertx.VertxPlatformHttpConsumer.processExchange(VertxPlatformHttpConsumer.java:244) > ~[camel-platform-http-vertx-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] > at > org.apache.camel.component.platform.http.vertx.VertxPlatformHttpConsumer.lambda$handleRequest$1(VertxPlatformHttpConsumer.java:212) > ~[camel-platform-http-vertx-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] > at > io.vertx.core.impl.ContextImpl.lambda$executeBlocking$0(ContextImpl.java:177) > ~[vertx-core-4.5.2.jar:4.5.2] > at > io.vertx.core.impl.ContextInternal.dispatch(ContextInternal.java:276) > ~[vertx-core-4.5.2.jar:4.5.2] > at > io.vertx.core.impl.ContextImpl.lambda$internalExecuteBlocking$2(ContextImpl.java:209) > ~[vertx-core-4.5.2.jar:4.5.2] > at > java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) > ~[?:?] > at > java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) > ~[?:?] >
[jira] [Created] (CAMEL-20623) camel-rest-openapi - Use another json validator that is jakartaee compatible
Claus Ibsen created CAMEL-20623: --- Summary: camel-rest-openapi - Use another json validator that is jakartaee compatible Key: CAMEL-20623 URL: https://issues.apache.org/jira/browse/CAMEL-20623 Project: Camel Issue Type: Improvement Components: camel-rest-openapi Reporter: Claus Ibsen Fix For: 4.6.0 The library it uses from atlassian is cr** as it has some static classloader hell, that uses old javax library, and you can't turn it off or configure it differently. java.lang.NoClassDefFoundError: javax/mail/internet/AddressException at com.github.fge.jsonschema.library.format.CommonFormatAttributesDictionary.(CommonFormatAttributesDictionary.java:56) ~[json-schema-validator-2.2.14.jar:?] at com.github.fge.jsonschema.library.format.DraftV3FormatAttributesDictionary.(DraftV3FormatAttributesDictionary.java:47) ~[json-schema-validator-2.2.14.jar:?] at com.github.fge.jsonschema.library.DraftV3Library.(DraftV3Library.java:36) ~[json-schema-validator-2.2.14.jar:?] at com.github.fge.jsonschema.cfg.ValidationConfigurationBuilder.(ValidationConfigurationBuilder.java:63) ~[json-schema-validator-2.2.14.jar:?] at com.github.fge.jsonschema.cfg.ValidationConfiguration.newBuilder(ValidationConfiguration.java:97) ~[json-schema-validator-2.2.14.jar:?] at com.github.fge.jsonschema.cfg.ValidationConfiguration.byDefault(ValidationConfiguration.java:107) ~[json-schema-validator-2.2.14.jar:?] at com.github.fge.jsonschema.main.JsonSchemaFactoryBuilder.(JsonSchemaFactoryBuilder.java:68) ~[json-schema-validator-2.2.14.jar:?] at com.github.fge.jsonschema.main.JsonSchemaFactory.newBuilder(JsonSchemaFactory.java:123) ~[json-schema-validator-2.2.14.jar:?] at com.atlassian.oai.validator.schema.SwaggerV20Library.schemaFactory(SwaggerV20Library.java:67) ~[swagger-request-validator-core-2.40.0.jar:?] at com.atlassian.oai.validator.schema.SwaggerV20Library.schemaFactory(SwaggerV20Library.java:56) ~[swagger-request-validator-core-2.40.0.jar:?] at com.atlassian.oai.validator.schema.SchemaValidator.(SchemaValidator.java:126) ~[swagger-request-validator-core-2.40.0.jar:?] at com.atlassian.oai.validator.OpenApiInteractionValidator.(OpenApiInteractionValidator.java:161) ~[swagger-request-validator-core-2.40.0.jar:?] at com.atlassian.oai.validator.OpenApiInteractionValidator.(OpenApiInteractionValidator.java:50) ~[swagger-request-validator-core-2.40.0.jar:?] at com.atlassian.oai.validator.OpenApiInteractionValidator$Builder.build(OpenApiInteractionValidator.java:674) ~[swagger-request-validator-core-2.40.0.jar:?] at org.apache.camel.component.rest.openapi.RestOpenApiEndpoint.configureRequestValidator(RestOpenApiEndpoint.java:822) ~[camel-rest-openapi-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at org.apache.camel.component.rest.openapi.RestOpenApiProcessor.process(RestOpenApiProcessor.java:101) ~[camel-rest-openapi-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.process(DefaultAsyncProcessorAwaitManager.java:82) ~[camel-base-engine-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at org.apache.camel.support.AsyncProcessorSupport.process(AsyncProcessorSupport.java:32) ~[camel-support-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at org.apache.camel.component.platform.http.vertx.VertxPlatformHttpConsumer.processExchange(VertxPlatformHttpConsumer.java:244) ~[camel-platform-http-vertx-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at org.apache.camel.component.platform.http.vertx.VertxPlatformHttpConsumer.lambda$handleRequest$1(VertxPlatformHttpConsumer.java:212) ~[camel-platform-http-vertx-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at io.vertx.core.impl.ContextImpl.lambda$executeBlocking$0(ContextImpl.java:177) ~[vertx-core-4.5.2.jar:4.5.2] at io.vertx.core.impl.ContextInternal.dispatch(ContextInternal.java:276) ~[vertx-core-4.5.2.jar:4.5.2] at io.vertx.core.impl.ContextImpl.lambda$internalExecuteBlocking$2(ContextImpl.java:209) ~[vertx-core-4.5.2.jar:4.5.2] at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?] at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?] at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [netty-common-4.1.106.Final.jar:4.1.106.Final] at java.base/java.lang.Thread.run(Thread.java:833) [?:?] Caused by: java.lang.ClassNotFoundException: javax.mail.internet.AddressException at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641) ~[?:?] at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188) ~[?:?]
[jira] [Commented] (CAMEL-20618) The Timer-component CamelTimerFiredTime related properties and headers are missing in 4.4.0
[
https://issues.apache.org/jira/browse/CAMEL-20618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17831335#comment-17831335
]
John Yin commented on CAMEL-20618:
--
Thanks [~davsclaus], as always! Sorry I missed that one in the migration guide.
> The Timer-component CamelTimerFiredTime related properties and headers are
> missing in 4.4.0
> ---
>
> Key: CAMEL-20618
> URL: https://issues.apache.org/jira/browse/CAMEL-20618
> Project: Camel
> Issue Type: Bug
>Affects Versions: 4.4.0
>Reporter: John Yin
>Priority: Major
>
> In 4.4.0, in a timer route, the exchange no longer carries properties/headers
> related to the fired time. The two assertions in the Groovy sample below
> will fail.
> from("timer://testRoute?repeatCount=1").process({
> assert it.in.getHeader('firedTime') != null
> assert it.getProperty('CamelTimerFiredTime') != null
> })
> In fact, the exchange has no properties and headers.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (CAMEL-20524) Harmonize camel main configuration properties across runtimes
[ https://issues.apache.org/jira/browse/CAMEL-20524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed CAMEL-20524. --- Resolution: Fixed > Harmonize camel main configuration properties across runtimes > - > > Key: CAMEL-20524 > URL: https://issues.apache.org/jira/browse/CAMEL-20524 > Project: Camel > Issue Type: Improvement > Components: camel-main, camel-quarkus, camel-spring-boot, > camel-spring-boot-starters >Reporter: Luca Burgazzoli >Assignee: Guillaume Nodet >Priority: Minor > > The camel-main module was originally designed to run make it easy to run > camel standalone without the need of a specific runtime (spring-boot, > quarkus, etc), but now camel-main is also a core component of camel-quarkus > and camel-spring-boot. > camel-main also offers a number of properties that can be configured to > configure camel-main, however, the runtimes may use some slight different > property naming/namespaces making things a little bit confusing. > As an example, camel-main defines a camel.main.routes-include-pattern > property to let camel discover routes, however in camel-spring-boot the same > property is camel.springboot..routes-include-pattern > Ideally, runtimes should honor camel-main property and reserve some specific > namespaces (i.e. camel.quarkus camel.springboot) for runtime specific options. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20622) camel-qdrant: add support for collection info
[ https://issues.apache.org/jira/browse/CAMEL-20622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske resolved CAMEL-20622. -- Resolution: Fixed Fixed with the linked PR. > camel-qdrant: add support for collection info > - > > Key: CAMEL-20622 > URL: https://issues.apache.org/jira/browse/CAMEL-20622 > Project: Camel > Issue Type: Improvement > Components: camel-qdrant >Affects Versions: 4.5.0 >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.6.0 > > > This can simplify checking if a collection exists or not: > > https://qdrant.tech/documentation/concepts/collections/#collection-info -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20621) camel-core - Single scheduled thread pool should have max queue of 1
Claus Ibsen created CAMEL-20621: --- Summary: camel-core - Single scheduled thread pool should have max queue of 1 Key: CAMEL-20621 URL: https://issues.apache.org/jira/browse/CAMEL-20621 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 4.6.0 Should be max pool size 1 like it is for regular single thread pool -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20622) camel-qdrant: add support for collection info
Otavio Rodolfo Piske created CAMEL-20622: Summary: camel-qdrant: add support for collection info Key: CAMEL-20622 URL: https://issues.apache.org/jira/browse/CAMEL-20622 Project: Camel Issue Type: Improvement Components: camel-qdrant Affects Versions: 4.5.0 Reporter: Otavio Rodolfo Piske Assignee: Otavio Rodolfo Piske Fix For: 4.6.0 This can simplify checking if a collection exists or not: https://qdrant.tech/documentation/concepts/collections/#collection-info -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-20557) camel-rest - Add openapi to rest-dsl so you can expose rest services from existing schema
[
https://issues.apache.org/jira/browse/CAMEL-20557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827046#comment-17827046
]
Claus Ibsen edited comment on CAMEL-20557 at 3/27/24 9:57 AM:
--
TODO: openapi into rest-dsl model *DONE*
TODO: configure some special new options in rest-dsl for openapi *DONE*
TODO: camel-rest-openapi add consumer *DONE*
TODO: api for creating consumer (impl in platform-http-vertx) *DONE*
TODO: operationId -> direct:operationId mapping (spi for plugin custom
implementations) *DONE*
TODO: option to return 204 for not yet implemented routes (so wont fail on
startup) *DONE*
TODO: option to validate all apis have route mapping (so can report which apis
that are missing) *DONE*
TODO: binding mode (and possible to override per operation so they have
different bindings)
TODO: request validation on|off *DONE*
TODO: documentation
TODO: example *DONE*
TODO: api-context-path to return the schema file as-is (change host url)
TODO: rest-openapi - specifciationUri should be String type for better tooling
support *DONE*
TODO: mock mode to load sample data from classpath/file system *DONE*
TODO: rest registry / managed rest registry
TODO: http summary to show all operations *DONE*
was (Author: davsclaus):
TODO: openapi into rest-dsl model *DONE*
TODO: configure some special new options in rest-dsl for openapi *DONE*
TODO: camel-rest-openapi add consumer *DONE*
TODO: api for creating consumer (impl in platform-http-vertx) *DONE*
TODO: operationId -> direct:operationId mapping (spi for plugin custom
implementations) *DONE*
TODO: option to return 204 for not yet implemented routes (so wont fail on
startup) *DONE*
TODO: option to validate all apis have route mapping (so can report which apis
that are missing) *DONE*
TODO: binding mode (and possible to override per operation so they have
different bindings)
TODO: request validation on|off *DONE*
TODO: documentation
TODO: example *DONE*
TODO: api-context-path to return the schema file as-is (change host url)
TODO: rest-openapi - specifciationUri should be String type for better tooling
support *DONE*
TODO: mock mode to load sample data from classpath/file system *DONE*
TODO: rest registry / managed rest registry
TODO: http summary to show all operations *DONE*
TODO: non managed producer cache
> 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.6.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)
[jira] [Comment Edited] (CAMEL-20557) camel-rest - Add openapi to rest-dsl so you can expose rest services from existing schema
[
https://issues.apache.org/jira/browse/CAMEL-20557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827046#comment-17827046
]
Claus Ibsen edited comment on CAMEL-20557 at 3/27/24 9:55 AM:
--
TODO: openapi into rest-dsl model *DONE*
TODO: configure some special new options in rest-dsl for openapi *DONE*
TODO: camel-rest-openapi add consumer *DONE*
TODO: api for creating consumer (impl in platform-http-vertx) *DONE*
TODO: operationId -> direct:operationId mapping (spi for plugin custom
implementations) *DONE*
TODO: option to return 204 for not yet implemented routes (so wont fail on
startup) *DONE*
TODO: option to validate all apis have route mapping (so can report which apis
that are missing) *DONE*
TODO: binding mode (and possible to override per operation so they have
different bindings)
TODO: request validation on|off *DONE*
TODO: documentation
TODO: example *DONE*
TODO: api-context-path to return the schema file as-is (change host url)
TODO: rest-openapi - specifciationUri should be String type for better tooling
support *DONE*
TODO: mock mode to load sample data from classpath/file system *DONE*
TODO: rest registry / managed rest registry
TODO: http summary to show all operations *DONE*
TODO: non managed producer cache
was (Author: davsclaus):
TODO: openapi into rest-dsl model *DONE*
TODO: configure some special new options in rest-dsl for openapi *DONE*
TODO: camel-rest-openapi add consumer *DONE*
TODO: api for creating consumer (impl in platform-http-vertx) *DONE*
TODO: operationId -> direct:operationId mapping (spi for plugin custom
implementations) *DONE*
TODO: option to return 204 for not yet implemented routes (so wont fail on
startup) *DONE*
TODO: option to validate all apis have route mapping (so can report which apis
that are missing) *DONE*
TODO: binding mode (and possible to override per operation so they have
different bindings)
TODO: request validation on|off *DONE*
TODO: documentation
TODO: example
TODO: api-context-path to return the schema file as-is (change host url)
TODO: rest-openapi - specifciationUri should be String type for better tooling
support *DONE*
TODO: mock mode to load sample data from classpath/file system *DONE*
TODO: rest registry / managed rest registry
TODO: http summary to show all operations *DONE*
TODO: non managed producer cache
> 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.6.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)
[jira] (CAMEL-20619) camel-jbang camel debug command is not working
[ https://issues.apache.org/jira/browse/CAMEL-20619 ] Vidhya Sagar Jeevendran deleted comment on CAMEL-20619: - was (Author: vsvdhsagar): May I know the issue ID, just for me watch the conversation. > camel-jbang camel debug command is not working > --- > > Key: CAMEL-20619 > URL: https://issues.apache.org/jira/browse/CAMEL-20619 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Affects Versions: 4.4.1 >Reporter: Vidhya Sagar Jeevendran >Priority: Major > > *camel run* is working as expected but *camel debug* is failing to run the > process with an exception. > > I tried with simple route (timer->log) both as yaml and java code in a > windows 11 machine. > > java.io.IOException: Cannot run program "camel": CreateProcess error=2, The > system cannot find the file specified > at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1143) > at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1073) > at > org.apache.camel.dsl.jbang.core.commands.Debug.runDebug(Debug.java:259) > at org.apache.camel.dsl.jbang.core.commands.Run.run(Run.java:788) > at org.apache.camel.dsl.jbang.core.commands.Run.runDebug(Run.java:338) > at > org.apache.camel.dsl.jbang.core.commands.Debug.doCall(Debug.java:135) > at > org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71) > at > org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37) > at picocli.CommandLine.executeUserObject(CommandLine.java:2041) > at picocli.CommandLine.access$1500(CommandLine.java:148) > at > picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2461) > at picocli.CommandLine$RunLast.handle(CommandLine.java:2453) > at picocli.CommandLine$RunLast.handle(CommandLine.java:2415) > at > picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2273) > at picocli.CommandLine$RunLast.execute(CommandLine.java:2417) > at picocli.CommandLine.execute(CommandLine.java:2170) > at > org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:159) > at > org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:58) > at main.CamelJBang.main(CamelJBang.java:36) > Caused by: java.io.IOException: CreateProcess error=2, The system cannot find > the file specified > at java.base/java.lang.ProcessImpl.create(Native Method) > at java.base/java.lang.ProcessImpl.(ProcessImpl.java:494) > at java.base/java.lang.ProcessImpl.start(ProcessImpl.java:159) > at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1110) > ... 18 more -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-20557) camel-rest - Add openapi to rest-dsl so you can expose rest services from existing schema
[
https://issues.apache.org/jira/browse/CAMEL-20557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827046#comment-17827046
]
Claus Ibsen edited comment on CAMEL-20557 at 3/27/24 9:45 AM:
--
TODO: openapi into rest-dsl model *DONE*
TODO: configure some special new options in rest-dsl for openapi *DONE*
TODO: camel-rest-openapi add consumer *DONE*
TODO: api for creating consumer (impl in platform-http-vertx) *DONE*
TODO: operationId -> direct:operationId mapping (spi for plugin custom
implementations) *DONE*
TODO: option to return 204 for not yet implemented routes (so wont fail on
startup) *DONE*
TODO: option to validate all apis have route mapping (so can report which apis
that are missing) *DONE*
TODO: binding mode (and possible to override per operation so they have
different bindings)
TODO: request validation on|off *DONE*
TODO: documentation
TODO: example
TODO: api-context-path to return the schema file as-is (change host url)
TODO: rest-openapi - specifciationUri should be String type for better tooling
support *DONE*
TODO: mock mode to load sample data from classpath/file system *DONE*
TODO: rest registry / managed rest registry
TODO: http summary to show all operations *DONE*
TODO: non managed producer cache
was (Author: davsclaus):
TODO: openapi into rest-dsl model
TODO: configure some special new options in rest-dsl for openapi
TODO: camel-rest-openapi add consumer *DONE*
TODO: api for creating consumer (impl in platform-http-vertx) *DONE*
TODO: operationId -> direct:operationId mapping (spi for plugin custom
implementations) *DONE*
TODO: option to return 204 for not yet implemented routes (so wont fail on
startup) *DONE*
TODO: option to validate all apis have route mapping (so can report which apis
that are missing) *DONE*
TODO: binding mode (and possible to override per operation so they have
different bindings)
TODO: request validation on|off *DONE*
TODO: documentation
TODO: example
TODO: api-context-path to return the schema file as-is (change host url)
TODO: rest-openapi - specifciationUri should be String type for better tooling
support *DONE*
TODO: mock mode to load sample data from classpath/file system *DONE*
TODO: rest registry / managed rest registry
TODO: http summary to show all operations *DONE*
TODO: non managed producer cache
> 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.6.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)
[jira] [Commented] (CAMEL-20524) Harmonize camel main configuration properties across runtimes
[ https://issues.apache.org/jira/browse/CAMEL-20524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17831246#comment-17831246 ] Luca Burgazzoli commented on CAMEL-20524: - so we are fine ! thank you [~gnodet] > Harmonize camel main configuration properties across runtimes > - > > Key: CAMEL-20524 > URL: https://issues.apache.org/jira/browse/CAMEL-20524 > Project: Camel > Issue Type: Improvement > Components: camel-main, camel-quarkus, camel-spring-boot, > camel-spring-boot-starters >Reporter: Luca Burgazzoli >Assignee: Guillaume Nodet >Priority: Minor > > The camel-main module was originally designed to run make it easy to run > camel standalone without the need of a specific runtime (spring-boot, > quarkus, etc), but now camel-main is also a core component of camel-quarkus > and camel-spring-boot. > camel-main also offers a number of properties that can be configured to > configure camel-main, however, the runtimes may use some slight different > property naming/namespaces making things a little bit confusing. > As an example, camel-main defines a camel.main.routes-include-pattern > property to let camel discover routes, however in camel-spring-boot the same > property is camel.springboot..routes-include-pattern > Ideally, runtimes should honor camel-main property and reserve some specific > namespaces (i.e. camel.quarkus camel.springboot) for runtime specific options. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-20557) camel-rest - Add openapi to rest-dsl so you can expose rest services from existing schema
[
https://issues.apache.org/jira/browse/CAMEL-20557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827046#comment-17827046
]
Claus Ibsen edited comment on CAMEL-20557 at 3/27/24 9:20 AM:
--
TODO: openapi into rest-dsl model
TODO: configure some special new options in rest-dsl for openapi
TODO: camel-rest-openapi add consumer *DONE*
TODO: api for creating consumer (impl in platform-http-vertx) *DONE*
TODO: operationId -> direct:operationId mapping (spi for plugin custom
implementations) *DONE*
TODO: option to return 204 for not yet implemented routes (so wont fail on
startup) *DONE*
TODO: option to validate all apis have route mapping (so can report which apis
that are missing) *DONE*
TODO: binding mode (and possible to override per operation so they have
different bindings)
TODO: request validation on|off *DONE*
TODO: documentation
TODO: example
TODO: api-context-path to return the schema file as-is (change host url)
TODO: rest-openapi - specifciationUri should be String type for better tooling
support *DONE*
TODO: mock mode to load sample data from classpath/file system *DONE*
TODO: rest registry / managed rest registry
TODO: http summary to show all operations *DONE*
TODO: non managed producer cache
was (Author: davsclaus):
TODO: openapi into rest-dsl model
TODO: camel-rest-openapi add consumer *DONE*
TODO: api for creating consumer (impl in platform-http-vertx) *DONE*
TODO: operationId -> direct:operationId mapping (spi for plugin custom
implementations) *DONE*
TODO: option to return 204 for not yet implemented routes (so wont fail on
startup) *DONE*
TODO: option to validate all apis have route mapping (so can report which apis
that are missing) *DONE*
TODO: binding mode (and possible to override per operation so they have
different bindings)
TODO: request validation on|off *DONE*
TODO: documentation
TODO: example
TODO: api-context-path to return the schema file as-is (change host url)
TODO: rest-openapi - specifciationUri should be String type for better tooling
support *DONE*
TODO: mock mode to load sample data from classpath/file system *DONE*
TODO: rest registry / managed rest registry
TODO: http summary to show all operations *DONE*
TODO: non managed producer cache
> 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.6.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)
[jira] [Comment Edited] (CAMEL-20557) camel-rest - Add openapi to rest-dsl so you can expose rest services from existing schema
[
https://issues.apache.org/jira/browse/CAMEL-20557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827046#comment-17827046
]
Claus Ibsen edited comment on CAMEL-20557 at 3/27/24 9:20 AM:
--
TODO: openapi into rest-dsl model
TODO: camel-rest-openapi add consumer *DONE*
TODO: api for creating consumer (impl in platform-http-vertx) *DONE*
TODO: operationId -> direct:operationId mapping (spi for plugin custom
implementations) *DONE*
TODO: option to return 204 for not yet implemented routes (so wont fail on
startup) *DONE*
TODO: option to validate all apis have route mapping (so can report which apis
that are missing) *DONE*
TODO: binding mode (and possible to override per operation so they have
different bindings)
TODO: request validation on|off *DONE*
TODO: documentation
TODO: example
TODO: api-context-path to return the schema file as-is (change host url)
TODO: rest-openapi - specifciationUri should be String type for better tooling
support *DONE*
TODO: mock mode to load sample data from classpath/file system *DONE*
TODO: rest registry / managed rest registry
TODO: http summary to show all operations *DONE*
TODO: non managed producer cache
was (Author: davsclaus):
TODO: openapi into rest-dsl model
TODO: camel-rest-openapi add consumer *DONE*
TODO: api for creating consumer (impl in platform-http-vertx) *DONE*
TODO: operationId -> direct:operationId mapping (spi for plugin custom
implementations) *DONE*
TODO: option to return 204 for not yet implemented routes (so wont fail on
startup) *DONE*
TODO: option to validate all apis have route mapping (so can report which apis
that are missing) *DONE*
TODO: binding mode (and possible to override per operation so they have
different bindings)
TODO: request validation on|off *DONE*
TODO: documentation
TODO: example
TODO: api-context-path to return the schema file as-is (change host url)
TODO: rest-openapi - specifciationUri should be String type for better tooling
support *DONE*
TODO: mock mode to load sample data from classpath/file system *DONE*
TODO: rest registry / managed rest registry
TODO: http summary to show all operations
TODO: non managed producer cache
> 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.6.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)
[jira] [Commented] (CAMEL-20524) Harmonize camel main configuration properties across runtimes
[
https://issues.apache.org/jira/browse/CAMEL-20524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17831233#comment-17831233
]
Guillaume Nodet commented on CAMEL-20524:
-
[~lb] I haven't seen any mismatch in {{camel-quarkus}} which fully reuses
{{camel-main}}. Are we fine, or is there more to do here ?
> Harmonize camel main configuration properties across runtimes
> -
>
> Key: CAMEL-20524
> URL: https://issues.apache.org/jira/browse/CAMEL-20524
> Project: Camel
> Issue Type: Improvement
> Components: camel-main, camel-quarkus, camel-spring-boot,
> camel-spring-boot-starters
>Reporter: Luca Burgazzoli
>Assignee: Guillaume Nodet
>Priority: Minor
>
> The camel-main module was originally designed to run make it easy to run
> camel standalone without the need of a specific runtime (spring-boot,
> quarkus, etc), but now camel-main is also a core component of camel-quarkus
> and camel-spring-boot.
> camel-main also offers a number of properties that can be configured to
> configure camel-main, however, the runtimes may use some slight different
> property naming/namespaces making things a little bit confusing.
> As an example, camel-main defines a camel.main.routes-include-pattern
> property to let camel discover routes, however in camel-spring-boot the same
> property is camel.springboot..routes-include-pattern
> Ideally, runtimes should honor camel-main property and reserve some specific
> namespaces (i.e. camel.quarkus camel.springboot) for runtime specific options.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
