[jira] [Updated] (CAMEL-18451) camel-azure-eventhubs: Add support for Azure-AD authentication
[ https://issues.apache.org/jira/browse/CAMEL-18451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat updated CAMEL-18451: - Fix Version/s: (was: 3.18.2) > camel-azure-eventhubs: Add support for Azure-AD authentication > -- > > Key: CAMEL-18451 > URL: https://issues.apache.org/jira/browse/CAMEL-18451 > Project: Camel > Issue Type: Improvement > Components: camel-azure-eventhubs >Affects Versions: 3.18.1 >Reporter: Babak Vahdat >Assignee: Babak Vahdat >Priority: Minor > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18452) Integrate azure-sdk-bom in a non-conflicting manner
[
https://issues.apache.org/jira/browse/CAMEL-18452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Babak Vahdat updated CAMEL-18452:
-
Fix Version/s: (was: 3.18.2)
> Integrate azure-sdk-bom in a non-conflicting manner
> ---
>
> Key: CAMEL-18452
> URL: https://issues.apache.org/jira/browse/CAMEL-18452
> Project: Camel
> Issue Type: Task
> Components: camel-azure
>Affects Versions: 3.18.1
>Reporter: Babak Vahdat
>Assignee: Babak Vahdat
>Priority: Minor
> Fix For: 3.19.0
>
>
> While working on CAMEL-18451 I ran into a conflicting Azure dependency issue.
> To reproduce it _just_ add the following dependency to
> {{camel-azure-eventhubs}} POM _without any_ other additional changes
> whatsoever:
> {code:java}
>
> com.azure
> azure-identity
> ${azure-identity-version}
>
> {code}
> and the integration test execution as mentioned
> [here|https://camel.apache.org/components/3.18.x/azure-eventhubs-component.html#_development_notes_important]
> will hang forever until it time outs through the {{maven-failsafe-plugin}}.
> This is because currently we have the following dependency versions on the
> main branch:
> {code:java}
> 5.11.2
> 1.5.1
> {code}
> The currently used {{azure-eventhubs}} version belongs to the BOM:
> [https://mvnrepository.com/artifact/com.azure/azure-sdk-bom/1.2.1]
> Whereas the current {{azure-identity}} version belongs to:
> [https://mvnrepository.com/artifact/com.azure/azure-sdk-bom/1.2.2]
> Each having potentially incompatible / non-matching own transitive dependency
> versions causing some sort of deadlock behaviour at runtime as explained
> above.
> We better need to make sure that whatever {{azure-XXX}} dependencies we have
> belong to the _same_ {{azure-sdk-bom}} version.
> I think it's possible to make use of {{azure-sdk-bom}} BOM in a
> non-conflicting manner.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18457) camel-resteasy - Deprecate
[ https://issues.apache.org/jira/browse/CAMEL-18457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18457. - Resolution: Fixed > camel-resteasy - Deprecate > -- > > Key: CAMEL-18457 > URL: https://issues.apache.org/jira/browse/CAMEL-18457 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18450) camel-jpa: improve to use transaction strategy in JpaMessageIdRepository
[ https://issues.apache.org/jira/browse/CAMEL-18450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18450: Fix Version/s: 3.19.0 > camel-jpa: improve to use transaction strategy in JpaMessageIdRepository > > > Key: CAMEL-18450 > URL: https://issues.apache.org/jira/browse/CAMEL-18450 > Project: Camel > Issue Type: Improvement > Components: camel-jpa >Affects Versions: 3.18.1, 3.19.0 >Reporter: Zheng Feng >Assignee: Zheng Feng >Priority: Major > Fix For: 3.19.0 > > > It needs to use transaction strategy in JpaMessageIdRepository when we have > introduce it in CAMEL. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18450) camel-jpa: improve to use transaction strategy in JpaMessageIdRepository
[ https://issues.apache.org/jira/browse/CAMEL-18450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17599964#comment-17599964 ] Claus Ibsen commented on CAMEL-18450: - I guess it may be nice to backport for 3.18.x > camel-jpa: improve to use transaction strategy in JpaMessageIdRepository > > > Key: CAMEL-18450 > URL: https://issues.apache.org/jira/browse/CAMEL-18450 > Project: Camel > Issue Type: Improvement > Components: camel-jpa >Affects Versions: 3.18.1, 3.19.0 >Reporter: Zheng Feng >Assignee: Zheng Feng >Priority: Major > Fix For: 3.19.0 > > > It needs to use transaction strategy in JpaMessageIdRepository when we have > introduce it in CAMEL. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18456) camel-test-infra: investigate consolidating usages of web server and servlets
[ https://issues.apache.org/jira/browse/CAMEL-18456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18456: Fix Version/s: 3.x > camel-test-infra: investigate consolidating usages of web server and servlets > - > > Key: CAMEL-18456 > URL: https://issues.apache.org/jira/browse/CAMEL-18456 > Project: Camel > Issue Type: Task > Components: camel-test-infra >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 3.x > > > There are many tests using Jetty, Undertow, Tomcat and others to run web > servers and/or servlet containers. Investigate consolidating this code into a > test infra module and cleaning up the components. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18449) camel-spring-boot - platform-http implementation
[ https://issues.apache.org/jira/browse/CAMEL-18449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-18449: --- Assignee: Federico Mariani > camel-spring-boot - platform-http implementation > > > Key: CAMEL-18449 > URL: https://issues.apache.org/jira/browse/CAMEL-18449 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Affects Versions: 3.18.0 >Reporter: Federico Mariani >Assignee: Federico Mariani >Priority: Major > Fix For: 3.19.0 > > Attachments: rest-post-consumer.zip > > > I was wondering if an implementation for platform-http can be provided in > camel-spring-boot platform-http-starter. Attached you can find a simple POC, > do you think it can be helpful/possible to have something like > _SpringBootPlatformHttpEngine_ implemented in camel-platform-http-starter? > In this way the > [camel-quarkus|https://camel.apache.org/camel-quarkus/2.11.x/reference/extensions/platform-http.html#_using_platform_http_via_camel_rest_dsl] > and camel-spring-boot behavior will be similar. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18437) Camel-bigquery: There is a difference in types between @name and ${name}
[
https://issues.apache.org/jira/browse/CAMEL-18437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18437:
Fix Version/s: 3.19.0
> Camel-bigquery: There is a difference in types between @name and ${name}
>
>
> Key: CAMEL-18437
> URL: https://issues.apache.org/jira/browse/CAMEL-18437
> Project: Camel
> Issue Type: Bug
> Components: camel-google-bigquery
>Affects Versions: 3.19.0
>Reporter: Jiri Ondrusek
>Assignee: Jiri Ondrusek
>Priority: Major
> Fix For: 3.19.0
>
>
> I noticed a undefined behavior when expanding coverage of google-bigquery in
> camel-quarkus ([ticket|https://github.com/apache/camel-quarkus/issues/3949]).
>
> Here is a relevant chapter from the [documentation|#_uri_format].]
>
> {quote} * parameters in form ${name} are extracted from message headers and
> formed the translated query
> * parameters in form @name are extracted from body or message headers and
> sent to Google Bigquery{quote}
> From my PoV is that in case of parameters in the header, it should not
> matter, whether _@name_ or _${name}_ is used.
> The behavior seems to be more complicated:
> * In case of _@name_ pattern, value types are dynamically resolved (see
> https://issues.apache.org/jira/browse/CAMEL-18382 for more details)
> * In case of {_}${name}{_}, value is inserted into the sql without any
> modification. Which behaves like "undefined".
> # If header value is an integer (like 4), sql is translated into {_}...
> VALUES (4) ...{_}, so it is interpreted as integer.
> # If header value is string with number inside (like "4"), sql is translated
> into {_}... VALUES (4) ...{_}, so it is interpreted as integer.
> # If the header is string (like "s4"), sql is translated into {_}... VALUES
> (s4) ...{_}, and the execution fails.
> It would make sense that the behavior of _@name_ and _${name}_ is the same
> and mainly the case 3 does not cause any failure.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18447) Camel-pubsub: com.google.api.gax.rpc.AsyncTaskException: Asynchronous task failed with real account
[
https://issues.apache.org/jira/browse/CAMEL-18447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18447:
Fix Version/s: 3.19.0
> Camel-pubsub: com.google.api.gax.rpc.AsyncTaskException: Asynchronous task
> failed with real account
> ---
>
> Key: CAMEL-18447
> URL: https://issues.apache.org/jira/browse/CAMEL-18447
> Project: Camel
> Issue Type: Bug
> Components: camel-google-pubsub
>Affects Versions: 3.18.2, 3.19.0
>Reporter: Jiri Ondrusek
>Assignee: Jiri Ondrusek
>Priority: Major
> Fix For: 3.19.0
>
>
> During fixation of [https://github.com/apache/camel-quarkus/issues/4062] I
> noticed regular exceptions shown only with real account (not with emulater):
>
> {code:java}
> Suppressed: com.google.api.gax.rpc.AsyncTaskException: Asynchronous task
> failed at
> com.google.api.gax.rpc.ApiExceptions.callAndTranslateApiException(ApiExceptions.java:57)
> at
> com.google.api.gax.rpc.UnaryCallable.call(UnaryCallable.java:112) {code}
> Exception shows that some connections is closed during the acking mechanism.
> It should be fixed. (To reproduce issue run i.e. run test from CQ with real
> account GooglePubsubTest#pubsubTopicProduceConsume)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18416) Upgrade to slf4j 2.0
[ https://issues.apache.org/jira/browse/CAMEL-18416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18416: Fix Version/s: 4.0 (was: 3.x) > Upgrade to slf4j 2.0 > > > Key: CAMEL-18416 > URL: https://issues.apache.org/jira/browse/CAMEL-18416 > Project: Camel > Issue Type: Dependency upgrade > Components: build system >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18385) camel-kamelet - Endpoint URIs from parameters could be passed as-is without uri encoding
[ https://issues.apache.org/jira/browse/CAMEL-18385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18385: Fix Version/s: 4.0 (was: 3.x) > camel-kamelet - Endpoint URIs from parameters could be passed as-is without > uri encoding > > > Key: CAMEL-18385 > URL: https://issues.apache.org/jira/browse/CAMEL-18385 > Project: Camel > Issue Type: Improvement > Components: camel-kamelet, camel-yaml-dsl >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.0 > > > CAMEL-18370 is related to this because the kamelet parameters become URI > parameters to the kamelet, which means that sensitive data such as username, > passwords must be protected by RAW() style to allow special chars such as + > to keep being +. > We could for yaml-dsl then build the uri parameters in a special way where we > store this as a bean (Map) and then let camel-kamelet lookup this bean via an > uuid, and then grab the data as-is to be used. > However this is a bit special when using yaml-dsl that can define endpoint > parameters in a special map like way. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18363) camel-couchdb - improve the documentation for updates
[ https://issues.apache.org/jira/browse/CAMEL-18363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18363: Fix Version/s: 3.x > camel-couchdb - improve the documentation for updates > - > > Key: CAMEL-18363 > URL: https://issues.apache.org/jira/browse/CAMEL-18363 > Project: Camel > Issue Type: Improvement > Components: camel-couchdb, documentation >Affects Versions: 3.18.0 >Reporter: Luca Ferrari >Priority: Minor > Fix For: 3.x > > > at the moment looking at the documentation it seems to update an entry you > need to provide an 'update' operation and 'doc_rev' id as headers, while this > is not really the way the update is implemented. > To perform an actual update using the couchdb connector you would need to set > the '_id' and '_rev' fields in the json payload sent to couchdb -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18372) camel-http-streaming - A http consumer that can read an endless stream
[ https://issues.apache.org/jira/browse/CAMEL-18372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18372: Priority: Minor (was: Major) > camel-http-streaming - A http consumer that can read an endless stream > -- > > Key: CAMEL-18372 > URL: https://issues.apache.org/jira/browse/CAMEL-18372 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Priority: Minor > Fix For: 3.x > > > We need a new http consumer component that can do HTTP GET/POST, TLS/SSL et > all and that then connects to a remote HTTP server and does http streaming. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18363) camel-couchdb - improve the documentation for updates
[ https://issues.apache.org/jira/browse/CAMEL-18363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18363: Component/s: documentation > camel-couchdb - improve the documentation for updates > - > > Key: CAMEL-18363 > URL: https://issues.apache.org/jira/browse/CAMEL-18363 > Project: Camel > Issue Type: Improvement > Components: camel-couchdb, documentation >Affects Versions: 3.18.0 >Reporter: Luca Ferrari >Priority: Minor > > at the moment looking at the documentation it seems to update an entry you > need to provide an 'update' operation and 'doc_rev' id as headers, while this > is not really the way the update is implemented. > To perform an actual update using the couchdb connector you would need to set > the '_id' and '_rev' fields in the json payload sent to couchdb -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18356) camel-resume-api: consolidade Kafka's single and multi strategies
[ https://issues.apache.org/jira/browse/CAMEL-18356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18356: Fix Version/s: 3.x > camel-resume-api: consolidade Kafka's single and multi strategies > - > > Key: CAMEL-18356 > URL: https://issues.apache.org/jira/browse/CAMEL-18356 > Project: Camel > Issue Type: Improvement > Components: camel-resume-api >Reporter: Otavio Rodolfo Piske >Priority: Major > Fix For: 3.x > > > We should only have one resume strategy in the Kafka component. It makes > everything simpler. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18334) camel-cxf-soap - platform-http as http transport
[ https://issues.apache.org/jira/browse/CAMEL-18334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18334: Priority: Minor (was: Major) > camel-cxf-soap - platform-http as http transport > > > Key: CAMEL-18334 > URL: https://issues.apache.org/jira/browse/CAMEL-18334 > Project: Camel > Issue Type: Improvement > Components: camel-cxf >Reporter: Claus Ibsen >Priority: Minor > Fix For: 3.x > > > With camel-cxf split into smaller JARs then we can look at if we can do a > platform-http adapter for CXF HTTP Transport, so we can use what comes from > the runtime platform such as vertx-http when using quarkus / jbang / camel-k. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18341) Upgrade from Codehaus Groovy 3.0.12 to Apache Groovy 4.x
[ https://issues.apache.org/jira/browse/CAMEL-18341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18341: Priority: Minor (was: Major) > Upgrade from Codehaus Groovy 3.0.12 to Apache Groovy 4.x > > > Key: CAMEL-18341 > URL: https://issues.apache.org/jira/browse/CAMEL-18341 > Project: Camel > Issue Type: Dependency upgrade >Affects Versions: 3.18.0 >Reporter: Aurélien Pupier >Priority: Minor > Fix For: 4.0 > > > Groovy 4.0.0 has been released at the beginning of 2022. it might be nice to > move to the latest version. > There is a long list of features and bug fixes > [http://groovy-lang.org/changelogs/changelog-4.0.0.html] > Maybe worth noticing it contains several fixes related to Java 17: > * [GROOVY-10391] - Default interface methods causing problems with java 17 > and groovy 3.0.9 > * [GROOVY-10405] - @AutoClone breaks in Java17 for File properties > * [GROOVY-10429] - StringBuilder misses setLength method in Java17 > Based on [https://groovy.apache.org/versioning.html] 3.x will have oen or two > bugfixxes release (in fact already 3 happened). So good chances that there > will be only security release of 3.x soon. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18341) Upgrade from Codehaus Groovy 3.0.12 to Apache Groovy 4.x
[ https://issues.apache.org/jira/browse/CAMEL-18341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18341: Fix Version/s: 4.0 > Upgrade from Codehaus Groovy 3.0.12 to Apache Groovy 4.x > > > Key: CAMEL-18341 > URL: https://issues.apache.org/jira/browse/CAMEL-18341 > Project: Camel > Issue Type: Dependency upgrade >Affects Versions: 3.18.0 >Reporter: Aurélien Pupier >Priority: Major > Fix For: 4.0 > > > Groovy 4.0.0 has been released at the beginning of 2022. it might be nice to > move to the latest version. > There is a long list of features and bug fixes > [http://groovy-lang.org/changelogs/changelog-4.0.0.html] > Maybe worth noticing it contains several fixes related to Java 17: > * [GROOVY-10391] - Default interface methods causing problems with java 17 > and groovy 3.0.9 > * [GROOVY-10405] - @AutoClone breaks in Java17 for File properties > * [GROOVY-10429] - StringBuilder misses setLength method in Java17 > Based on [https://groovy.apache.org/versioning.html] 3.x will have oen or two > bugfixxes release (in fact already 3 happened). So good chances that there > will be only security release of 3.x soon. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18326) google-mail-stream - message body as raw
[
https://issues.apache.org/jira/browse/CAMEL-18326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18326:
Summary: google-mail-stream - message body as raw (was: google-mail-stream)
> google-mail-stream - message body as raw
>
>
> Key: CAMEL-18326
> URL: https://issues.apache.org/jira/browse/CAMEL-18326
> Project: Camel
> Issue Type: Improvement
> Components: camel-google-mail-stream
>Affects Versions: 3.16.0
>Reporter: Jérôme GARCIA
>Priority: Minor
> Labels: camel-core, google
> Fix For: 3.x
>
>
> Hello,
>
> In *google-mail-stream* component, the mail body is displayed as plain text
> and is not easy to manipulate the data.
> The component should add the possibility to change this behavior and
> displayed a standardize object (JSON or other).
>
> {code:java}
> // code placeholder
> from('google-mail-stream:index?' +
> 'applicationName={{camel-app-name}}&' +
> 'accessToken={{gmail.client.access.token}}&' +
> 'refreshToken={{gmail.client.access.refresh.token}}&' +
> 'clientId={{gmail.client.id}}&' +
> 'query=is:unread&' +
> 'clientSecret={{gmail.client.secret}}')
> .log('body: ${body}') {code}
>
> Here is the format received by google-mail component for example:
>
> {code:java}
> // code placeholder
> {
> "historyId": "",
> "id": "",
> "internalDate": "",
> "labelIds": [ ],
> "payload": {
> "body": {
> "size": 0
> },
> "filename": "",
> "headers": [
> {
> "name": "",
> "value": ""
> }
> ],
> "mimeType": "",
> "partId": "",
> "parts": [
> {
> "body": {
> "data": "",
> "size": 241
> },
> "filename": "",
> "headers": [
> {
> "name": "",
> "value": ""
> }
> ],
> "mimeType": "",
> "partId": ""
> },
> {
> "body": {
> "data": "",
> "size": 2519
> },
> "filename": "",
> "headers": [
> {
> "name": "",
> "value": ""
> }
> ],
> "mimeType": "",
> "partId": ""
> }
> ]
> },
> "sizeEstimate": 3513,
> "snippet": "",
> "threadId": ""
> }
> {code}
>
> What do you think?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18326) google-mail-stream
[
https://issues.apache.org/jira/browse/CAMEL-18326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18326:
Fix Version/s: 3.x
> google-mail-stream
> --
>
> Key: CAMEL-18326
> URL: https://issues.apache.org/jira/browse/CAMEL-18326
> Project: Camel
> Issue Type: Improvement
> Components: camel-google-mail-stream
>Affects Versions: 3.16.0
>Reporter: Jérôme GARCIA
>Priority: Minor
> Labels: camel-core, google
> Fix For: 3.x
>
>
> Hello,
>
> In *google-mail-stream* component, the mail body is displayed as plain text
> and is not easy to manipulate the data.
> The component should add the possibility to change this behavior and
> displayed a standardize object (JSON or other).
>
> {code:java}
> // code placeholder
> from('google-mail-stream:index?' +
> 'applicationName={{camel-app-name}}&' +
> 'accessToken={{gmail.client.access.token}}&' +
> 'refreshToken={{gmail.client.access.refresh.token}}&' +
> 'clientId={{gmail.client.id}}&' +
> 'query=is:unread&' +
> 'clientSecret={{gmail.client.secret}}')
> .log('body: ${body}') {code}
>
> Here is the format received by google-mail component for example:
>
> {code:java}
> // code placeholder
> {
> "historyId": "",
> "id": "",
> "internalDate": "",
> "labelIds": [ ],
> "payload": {
> "body": {
> "size": 0
> },
> "filename": "",
> "headers": [
> {
> "name": "",
> "value": ""
> }
> ],
> "mimeType": "",
> "partId": "",
> "parts": [
> {
> "body": {
> "data": "",
> "size": 241
> },
> "filename": "",
> "headers": [
> {
> "name": "",
> "value": ""
> }
> ],
> "mimeType": "",
> "partId": ""
> },
> {
> "body": {
> "data": "",
> "size": 2519
> },
> "filename": "",
> "headers": [
> {
> "name": "",
> "value": ""
> }
> ],
> "mimeType": "",
> "partId": ""
> }
> ]
> },
> "sizeEstimate": 3513,
> "snippet": "",
> "threadId": ""
> }
> {code}
>
> What do you think?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18316) camel-core 3.18 not compatible with Jakarta Activation framework 2.0
[ https://issues.apache.org/jira/browse/CAMEL-18316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17599962#comment-17599962 ] Claus Ibsen commented on CAMEL-18316: - Camel 4 is where we do all the JEE10 and javax -> jakarta migration > camel-core 3.18 not compatible with Jakarta Activation framework 2.0 > > > Key: CAMEL-18316 > URL: https://issues.apache.org/jira/browse/CAMEL-18316 > Project: Camel > Issue Type: Dependency upgrade > Components: came-core >Affects Versions: 3.18.0 > Environment: JDK 17 >Reporter: Soumik Das >Priority: Major > > We are upgrading from JAF 1.2 to Jakarta Activation (JAF 2.0) for JDK 17. It > turns out camel 3.18 does not support jakarta.activation. When can we expect > an upgrade? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18320) camel-core - Move xtokenize language into camel-stax
[ https://issues.apache.org/jira/browse/CAMEL-18320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18320: Priority: Minor (was: Major) > camel-core - Move xtokenize language into camel-stax > > > Key: CAMEL-18320 > URL: https://issues.apache.org/jira/browse/CAMEL-18320 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Priority: Minor > Fix For: 3.19.0 > > > This language needs a StAX parser that is not out of the box in the JDK that > works, instead you need to use woostock which we provide via camel-stax. > So lets move the language there so it will work OOTB for everyone. > CEQ has a special note about this at: > https://camel.apache.org/camel-quarkus/2.11.x/reference/extensions/xml-jaxp.html#_usage -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18309) Allow to disable timeouts with Camel test
[
https://issues.apache.org/jira/browse/CAMEL-18309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18309:
Priority: Minor (was: Major)
> Allow to disable timeouts with Camel test
> -
>
> Key: CAMEL-18309
> URL: https://issues.apache.org/jira/browse/CAMEL-18309
> Project: Camel
> Issue Type: New Feature
> Components: camel-test
>Affects Versions: 3.18.0
>Reporter: Aurélien Pupier
>Priority: Minor
>
> When debugging a Camel test, it would be convenient to be able to disable
> timeouts.
> Similar feature specific to JUnit test
> [https://junit.org/junit5/docs/current/user-guide/#writing-tests-declarative-timeouts-mode]
> I spotted
> [NotifyBuilder|https://www.javadoc.io/doc/org.apache.camel/camel-core-model/latest/org/apache/camel/builder/NotifyBuilder.html#waitTime(long)]
> which is used in test that has timeouts. Need to lookup if there are other
> ways to have timeouts in test
> I think there would 2 main categories:
> * when Java debugging is used. In this case, maybe can reuse same heurisitic
> than for JUnit
> * when Camel debugging. In this case, the heuristic to detect the debug must
> be different.
> maybe a configuration parameter _camel.test.execution.timeout.mode_ can be
> provided. With potential values {_}enabled{_}, {_}disabled{_},
> _disabled_on_debug._
> The default mode for JUnit is {_}enabled{_}. So I guess we should use it too.
> Maybe worth defaulting to _disabled_on_debug_ when _camel-debug_ is on
> classpath.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18309) camel-debug - Allow to disable timeouts with Camel test
[
https://issues.apache.org/jira/browse/CAMEL-18309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18309:
Summary: camel-debug - Allow to disable timeouts with Camel test (was:
Allow to disable timeouts with Camel test)
> camel-debug - Allow to disable timeouts with Camel test
> ---
>
> Key: CAMEL-18309
> URL: https://issues.apache.org/jira/browse/CAMEL-18309
> Project: Camel
> Issue Type: New Feature
> Components: camel-test
>Affects Versions: 3.18.0
>Reporter: Aurélien Pupier
>Priority: Minor
> Fix For: 3.x
>
>
> When debugging a Camel test, it would be convenient to be able to disable
> timeouts.
> Similar feature specific to JUnit test
> [https://junit.org/junit5/docs/current/user-guide/#writing-tests-declarative-timeouts-mode]
> I spotted
> [NotifyBuilder|https://www.javadoc.io/doc/org.apache.camel/camel-core-model/latest/org/apache/camel/builder/NotifyBuilder.html#waitTime(long)]
> which is used in test that has timeouts. Need to lookup if there are other
> ways to have timeouts in test
> I think there would 2 main categories:
> * when Java debugging is used. In this case, maybe can reuse same heurisitic
> than for JUnit
> * when Camel debugging. In this case, the heuristic to detect the debug must
> be different.
> maybe a configuration parameter _camel.test.execution.timeout.mode_ can be
> provided. With potential values {_}enabled{_}, {_}disabled{_},
> _disabled_on_debug._
> The default mode for JUnit is {_}enabled{_}. So I guess we should use it too.
> Maybe worth defaulting to _disabled_on_debug_ when _camel-debug_ is on
> classpath.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18316) camel-core 3.18 not compatible with Jakarta Activation framework 2.0
[ https://issues.apache.org/jira/browse/CAMEL-18316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18316. - Resolution: Information Provided > camel-core 3.18 not compatible with Jakarta Activation framework 2.0 > > > Key: CAMEL-18316 > URL: https://issues.apache.org/jira/browse/CAMEL-18316 > Project: Camel > Issue Type: Dependency upgrade > Components: came-core >Affects Versions: 3.18.0 > Environment: JDK 17 >Reporter: Soumik Das >Priority: Major > > We are upgrading from JAF 1.2 to Jakarta Activation (JAF 2.0) for JDK 17. It > turns out camel 3.18 does not support jakarta.activation. When can we expect > an upgrade? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18309) Allow to disable timeouts with Camel test
[
https://issues.apache.org/jira/browse/CAMEL-18309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18309:
Fix Version/s: 3.x
> Allow to disable timeouts with Camel test
> -
>
> Key: CAMEL-18309
> URL: https://issues.apache.org/jira/browse/CAMEL-18309
> Project: Camel
> Issue Type: New Feature
> Components: camel-test
>Affects Versions: 3.18.0
>Reporter: Aurélien Pupier
>Priority: Minor
> Fix For: 3.x
>
>
> When debugging a Camel test, it would be convenient to be able to disable
> timeouts.
> Similar feature specific to JUnit test
> [https://junit.org/junit5/docs/current/user-guide/#writing-tests-declarative-timeouts-mode]
> I spotted
> [NotifyBuilder|https://www.javadoc.io/doc/org.apache.camel/camel-core-model/latest/org/apache/camel/builder/NotifyBuilder.html#waitTime(long)]
> which is used in test that has timeouts. Need to lookup if there are other
> ways to have timeouts in test
> I think there would 2 main categories:
> * when Java debugging is used. In this case, maybe can reuse same heurisitic
> than for JUnit
> * when Camel debugging. In this case, the heuristic to detect the debug must
> be different.
> maybe a configuration parameter _camel.test.execution.timeout.mode_ can be
> provided. With potential values {_}enabled{_}, {_}disabled{_},
> _disabled_on_debug._
> The default mode for JUnit is {_}enabled{_}. So I guess we should use it too.
> Maybe worth defaulting to _disabled_on_debug_ when _camel-debug_ is on
> classpath.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18314) camel-core - Generic vault property function that delegates to provider available
[ https://issues.apache.org/jira/browse/CAMEL-18314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18314: Fix Version/s: 3.x (was: 3.19.0) > camel-core - Generic vault property function that delegates to provider > available > - > > Key: CAMEL-18314 > URL: https://issues.apache.org/jira/browse/CAMEL-18314 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.x > > > When using vault/secrets then you have to specify aws, azure, ... currently. > But you may want to use a generic term `vault` that then delegates to a > provider at runtime, so you can run the same route on aws, azure, local, etc. > https://camel.apache.org/blog/2022/07/secrets-properties-functions-part-2/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18305) Make XML Dumper work XML-IO
[
https://issues.apache.org/jira/browse/CAMEL-18305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18305:
Fix Version/s: 4.0
> Make XML Dumper work XML-IO
> ---
>
> Key: CAMEL-18305
> URL: https://issues.apache.org/jira/browse/CAMEL-18305
> Project: Camel
> Issue Type: Wish
> Components: camel-jaxb
>Affects Versions: 3.18.0
>Reporter: Raymond
>Priority: Minor
> Fix For: 4.0
>
>
> I use the XML Dumper. But now in 3.18.0 it says:
> Cannot find ModelToXMLDumper on classpath. Add camel-xml-jaxb to classpath.
> It's true that I don't have camel-xml-jaxb on the classpath. I do however
> have:
> camel-xml-io
> On my classpath. Would be nice if ModelToXMLDumper would work with the
> camel-xml-io dependency also.
> :{{{}Cannot find ModelToXMLDumper on classpath. Add camel-xml-jaxb to
> classpath.{}}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18305) Make XML Dumper work XML-IO
[
https://issues.apache.org/jira/browse/CAMEL-18305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18305:
Component/s: camel-core
(was: camel-jaxb)
> Make XML Dumper work XML-IO
> ---
>
> Key: CAMEL-18305
> URL: https://issues.apache.org/jira/browse/CAMEL-18305
> Project: Camel
> Issue Type: Wish
> Components: camel-core
>Affects Versions: 3.18.0
>Reporter: Raymond
>Priority: Minor
> Fix For: 4.0
>
>
> I use the XML Dumper. But now in 3.18.0 it says:
> Cannot find ModelToXMLDumper on classpath. Add camel-xml-jaxb to classpath.
> It's true that I don't have camel-xml-jaxb on the classpath. I do however
> have:
> camel-xml-io
> On my classpath. Would be nice if ModelToXMLDumper would work with the
> camel-xml-io dependency also.
> :{{{}Cannot find ModelToXMLDumper on classpath. Add camel-xml-jaxb to
> classpath.{}}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18304) Kafka SSLContextParameters support to resolve classpath Keystore and Truststore
[
https://issues.apache.org/jira/browse/CAMEL-18304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18304:
Fix Version/s: 3.x
> Kafka SSLContextParameters support to resolve classpath Keystore and
> Truststore
>
>
> Key: CAMEL-18304
> URL: https://issues.apache.org/jira/browse/CAMEL-18304
> Project: Camel
> Issue Type: New Feature
> Components: camel-kafka
>Reporter: Aniket Jadhav
>Priority: Major
> Labels: kafka, sslContextParameters
> Fix For: 3.x
>
>
> Kafka component does have the provision to provide bean of
> org.apache.camel.support.jsse.SSLContextParameters as a sslContextParameters
> property.
> But it does not support parsing the value for Keystore and TrustStore like
> path , password etc also not loads it from classpath like in HttpComponent.
> Camel Version- 3.14.3
> Example - I have created bean of sslContextParameter and passing it to Kafka
> Component as below
> {code:java}
>
>
> password="{{keystore.password}}" />
>
>
> password="{{truststore.password}}" />
>
> xmlns="http://camel.apache.org/schema/blueprint; id="ctx"
> streamCache="true" useMDCLogging="true">
>
> location="classpath:config_${ENV}.properties,classpath:config.properties"
> ignoreMissingLocation="true" propertiesParserRef="jasypt" />
>
>
>
> value="#sslContextParameters" />
>
>
>
>
>
>
>
> {code}
> As It does not support to load Keystore and Truststore from classpath and not
> parsing properties we can't use property placeholder and classpath resources.
> We should invoke below method to load Keystore from class path and to use
> property place holders for passing password.
> https://github.com/apache/camel/blob/main/core/camel-api/src/main/java/org/apache/camel/support/jsse/KeyStoreParameters.java#L159
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18301) Component for Sharepoint Lists (Office 365)
[ https://issues.apache.org/jira/browse/CAMEL-18301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18301: Fix Version/s: Future > Component for Sharepoint Lists (Office 365) > --- > > Key: CAMEL-18301 > URL: https://issues.apache.org/jira/browse/CAMEL-18301 > Project: Camel > Issue Type: New Feature >Reporter: Adrien SALES >Priority: Minor > Labels: features > Fix For: Future > > > h1. Context > > more and more users store data in Sharepoint LIsts on sharepointOnline. The > tricky part comes when we are asked to perform integrations with these DATAs. > They are served as REST APIs, OIDC and oAUth options are available but you be > awesome to be able to grab these datas as easily as we can with the JDBC > component for example. > > Our main usecase by the way is to copy data from SharepointLists to JDBC data > sources... or Kafka topics. > > h1. Feature request > > * Add the Microsoft Sharepoint List component to core components > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-13573) Parquet Dataformat: supporting parquet files in marshal / unmarshal
[ https://issues.apache.org/jira/browse/CAMEL-13573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onder Sezgin reassigned CAMEL-13573: Assignee: Onder Sezgin > Parquet Dataformat: supporting parquet files in marshal / unmarshal > --- > > Key: CAMEL-13573 > URL: https://issues.apache.org/jira/browse/CAMEL-13573 > Project: Camel > Issue Type: New Feature >Reporter: Matteo Redaelli >Assignee: Onder Sezgin >Priority: Major > Fix For: 3.x > > > It would be useweful to read / store data (marshal / unmarshal) in parquet > format ([https://parquet.apache.org/]). > It is widely used in bigdata projects / datalakes > > I did not found any info about it in the documentation... > > Thanks > Matteo -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18298) camel-jbang - Add support for @Startup beans
[ https://issues.apache.org/jira/browse/CAMEL-18298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18298: Priority: Minor (was: Major) > camel-jbang - Add support for @Startup beans > > > Key: CAMEL-18298 > URL: https://issues.apache.org/jira/browse/CAMEL-18298 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Priority: Minor > Fix For: 3.x > > > Lets see if we can detect @Startup bean classes that has methods that can > produce beans that customize camel components etc, which we should detect and > register into camel. > We do have some support for @Produce already today. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18298) camel-jbang - Add support for @Startup beans
[ https://issues.apache.org/jira/browse/CAMEL-18298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18298: Fix Version/s: 3.x (was: 3.19.0) > camel-jbang - Add support for @Startup beans > > > Key: CAMEL-18298 > URL: https://issues.apache.org/jira/browse/CAMEL-18298 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.x > > > Lets see if we can detect @Startup bean classes that has methods that can > produce beans that customize camel components etc, which we should detect and > register into camel. > We do have some support for @Produce already today. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18290) Deploy CSB examples on openshift cluster using odo.
[ https://issues.apache.org/jira/browse/CAMEL-18290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18290. - Resolution: Won't Do > Deploy CSB examples on openshift cluster using odo. > --- > > Key: CAMEL-18290 > URL: https://issues.apache.org/jira/browse/CAMEL-18290 > Project: Camel > Issue Type: Task > Components: camel-spring-boot, examples >Reporter: Vaishnavi R >Assignee: Vaishnavi R >Priority: Major > Fix For: 3.19.0 > > > To deploy the examples on openshift using odo and devfile.yaml. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18284) Provide command to set default value to use by Camel JBang
[ https://issues.apache.org/jira/browse/CAMEL-18284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17599951#comment-17599951 ] Claus Ibsen commented on CAMEL-18284: - Yeah some kind of ~/.camel-jbang/config.properties where you can set some defaults. It is a bit tricker to send that camel version as its jbang controlling this, not camel > Provide command to set default value to use by Camel JBang > -- > > Key: CAMEL-18284 > URL: https://issues.apache.org/jira/browse/CAMEL-18284 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Affects Versions: 3.18.0 >Reporter: Aurélien Pupier >Priority: Minor > Fix For: 3.x > > > it will avoid having to set all the time the version through > -Dcamel.jbang.version=XXX or to change an hidden file manually. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18284) Provide command to set default value to use by Camel JBang
[ https://issues.apache.org/jira/browse/CAMEL-18284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18284: Fix Version/s: 3.x > Provide command to set default value to use by Camel JBang > -- > > Key: CAMEL-18284 > URL: https://issues.apache.org/jira/browse/CAMEL-18284 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Affects Versions: 3.18.0 >Reporter: Aurélien Pupier >Priority: Minor > Fix For: 3.x > > > it will avoid having to set all the time the version through > -Dcamel.jbang.version=XXX or to change an hidden file manually. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18280) Reuse AWS localstack docker image
[ https://issues.apache.org/jira/browse/CAMEL-18280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18280: Fix Version/s: 3.x > Reuse AWS localstack docker image > - > > Key: CAMEL-18280 > URL: https://issues.apache.org/jira/browse/CAMEL-18280 > Project: Camel > Issue Type: Improvement >Reporter: Federico Mariani >Assignee: Otavio Rodolfo Piske >Priority: Minor > Fix For: 3.x > > > AWS IT tests execution is slow mostly due to localstack docker image > restarts, can the docker image be reused via testcontainer? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18277) Google Pubsub: MessageOrderingIT test does not work with real account
[
https://issues.apache.org/jira/browse/CAMEL-18277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18277:
Priority: Minor (was: Major)
> Google Pubsub: MessageOrderingIT test does not work with real account
> -
>
> Key: CAMEL-18277
> URL: https://issues.apache.org/jira/browse/CAMEL-18277
> Project: Camel
> Issue Type: Bug
> Components: camel-google-pubsub, tests
>Affects Versions: 3.18.0
>Reporter: Jiri Ondrusek
>Assignee: Jiri Ondrusek
>Priority: Minor
>
> I'm working on test coverage of _camel-pubsub_ extension in Camel-quarkus
> ([issue|[https://github.com/apache/camel-quarkus/issues/3910]).]
> I noticed:
> * There is no easy way of running integration tests with the real account.
> It would be nice to have an option to export for example a several env.
> properties (like export GOOGLE_APPLICATION_CREDENTIALS=.. and export
> GOOGLE_PROJECT_ID=...) and allow execution of the tests with the real account.
> * _MessageOrderingIT_ does not work with the real cloud account. You can see
> an exception, which is probably caused by the use of regional endpoint.
> {code:java}
> java.util.concurrent.ExecutionException:
> com.google.api.gax.rpc.UnauthenticatedException:
> io.grpc.StatusRuntimeException: UNAUTHENTICATED: Request had invalid
> authentication credentials. Expected OAuth 2 access token, login cookie or
> other valid authentication credential. See
> https://developers.google.com/identity/sign-in/web/devconsole-project.
> at
> com.google.common.util.concurrent.AbstractFuture.getDoneValue(AbstractFuture.java:588)
> at
> com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:567)
> at com.google.api.core.AbstractApiFuture.get(AbstractApiFuture.java:55)
> at
> org.apache.camel.component.google.pubsub.GooglePubsubProducer.send(GooglePubsubProducer.java:117)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18276) azure-service-bus component does not support session
[ https://issues.apache.org/jira/browse/CAMEL-18276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18276: Fix Version/s: 3.x > azure-service-bus component does not support session > > > Key: CAMEL-18276 > URL: https://issues.apache.org/jira/browse/CAMEL-18276 > Project: Camel > Issue Type: New Feature > Components: camel-azure >Affects Versions: 3.18.0 >Reporter: Jean-Benoît >Priority: Minor > Fix For: 3.x > > > Hello, > From what I could tell, the azure-servicebus component does not support > sessions. Any chance this can be added in an upcoming release? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18277) Google Pubsub: MessageOrderingIT test does not work with real account
[
https://issues.apache.org/jira/browse/CAMEL-18277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18277:
Fix Version/s: 3.x
> Google Pubsub: MessageOrderingIT test does not work with real account
> -
>
> Key: CAMEL-18277
> URL: https://issues.apache.org/jira/browse/CAMEL-18277
> Project: Camel
> Issue Type: Bug
> Components: camel-google-pubsub, tests
>Affects Versions: 3.18.0
>Reporter: Jiri Ondrusek
>Assignee: Jiri Ondrusek
>Priority: Minor
> Fix For: 3.x
>
>
> I'm working on test coverage of _camel-pubsub_ extension in Camel-quarkus
> ([issue|[https://github.com/apache/camel-quarkus/issues/3910]).]
> I noticed:
> * There is no easy way of running integration tests with the real account.
> It would be nice to have an option to export for example a several env.
> properties (like export GOOGLE_APPLICATION_CREDENTIALS=.. and export
> GOOGLE_PROJECT_ID=...) and allow execution of the tests with the real account.
> * _MessageOrderingIT_ does not work with the real cloud account. You can see
> an exception, which is probably caused by the use of regional endpoint.
> {code:java}
> java.util.concurrent.ExecutionException:
> com.google.api.gax.rpc.UnauthenticatedException:
> io.grpc.StatusRuntimeException: UNAUTHENTICATED: Request had invalid
> authentication credentials. Expected OAuth 2 access token, login cookie or
> other valid authentication credential. See
> https://developers.google.com/identity/sign-in/web/devconsole-project.
> at
> com.google.common.util.concurrent.AbstractFuture.getDoneValue(AbstractFuture.java:588)
> at
> com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:567)
> at com.google.api.core.AbstractApiFuture.get(AbstractApiFuture.java:55)
> at
> org.apache.camel.component.google.pubsub.GooglePubsubProducer.send(GooglePubsubProducer.java:117)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18280) Reuse AWS localstack docker image
[ https://issues.apache.org/jira/browse/CAMEL-18280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18280: Component/s: tests > Reuse AWS localstack docker image > - > > Key: CAMEL-18280 > URL: https://issues.apache.org/jira/browse/CAMEL-18280 > Project: Camel > Issue Type: Improvement > Components: tests >Reporter: Federico Mariani >Assignee: Otavio Rodolfo Piske >Priority: Minor > Fix For: 3.x > > > AWS IT tests execution is slow mostly due to localstack docker image > restarts, can the docker image be reused via testcontainer? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18276) azure-service-bus component does not support session
[ https://issues.apache.org/jira/browse/CAMEL-18276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18276: Priority: Minor (was: Major) > azure-service-bus component does not support session > > > Key: CAMEL-18276 > URL: https://issues.apache.org/jira/browse/CAMEL-18276 > Project: Camel > Issue Type: New Feature > Components: camel-azure >Affects Versions: 3.18.0 >Reporter: Jean-Benoît >Priority: Minor > > Hello, > From what I could tell, the azure-servicebus component does not support > sessions. Any chance this can be added in an upcoming release? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18276) azure-service-bus component does not support session
[ https://issues.apache.org/jira/browse/CAMEL-18276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17599950#comment-17599950 ] Claus Ibsen commented on CAMEL-18276: - Can you provide more details about session ( maybe link to azure ) and some more details on what that would look like in camel > azure-service-bus component does not support session > > > Key: CAMEL-18276 > URL: https://issues.apache.org/jira/browse/CAMEL-18276 > Project: Camel > Issue Type: New Feature > Components: camel-azure >Affects Versions: 3.18.0 >Reporter: Jean-Benoît >Priority: Major > > Hello, > From what I could tell, the azure-servicebus component does not support > sessions. Any chance this can be added in an upcoming release? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18261) Add connection parameters to MongoDB component
[
https://issues.apache.org/jira/browse/CAMEL-18261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18261:
Fix Version/s: 3.x
> Add connection parameters to MongoDB component
> --
>
> Key: CAMEL-18261
> URL: https://issues.apache.org/jira/browse/CAMEL-18261
> Project: Camel
> Issue Type: Improvement
> Components: camel-mongodb
>Reporter: ALEXANDRE DAVI ZANELATTO
>Priority: Minor
> Fix For: 3.x
>
>
> Add the following options to mongodb component:
> * {*}ssl{*}: A boolean to enable or disables TLS/SSL for the connection;
> * {*}directConnection{*}: Allow a driver to force a Single topology type
> with a connection string containing one host;
> * {*}retryWrites{*}: Enable retryable writes.
> These options are currently missing from the mongodb endpoint URI.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18254) camel-jbang - Kamelets should only log explicit configured options on startup
[ https://issues.apache.org/jira/browse/CAMEL-18254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18254: Fix Version/s: 3.x (was: 3.19.0) > camel-jbang - Kamelets should only log explicit configured options on startup > - > > Key: CAMEL-18254 > URL: https://issues.apache.org/jira/browse/CAMEL-18254 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.x > > > We should look at making kamelets not log their default options, as that is a > bit noisy. > For example running > camel-kamelets-examples/jbang/metrics main *1 ❯ camel run metrics.yaml > --console > You see > 2022-07-01 12:57:44.883 INFO 54705 --- [ main] > org.apache.camel.main.BaseMainSupport: Property-placeholders summary > 2022-07-01 12:57:44.883 INFO 54705 --- [ main] > org.apache.camel.main.BaseMainSupport: [timer-source.kamelet.yaml] > period=1000 > 2022-07-01 12:57:44.884 INFO 54705 --- [ main] > org.apache.camel.main.BaseMainSupport: [timer-source.kamelet.yaml] > message=hello > 2022-07-01 12:57:44.884 INFO 54705 --- [ main] > org.apache.camel.main.BaseMainSupport: [timer-source.kamelet.yaml] > contentType=text/plain > 2022-07-01 12:57:44.884 INFO 54705 --- [ main] > org.apache.camel.main.BaseMainSupport: [timer-source.kamelet.yaml] > templateId=timer-source > The only specific option we use in this example is message=hello. The other > values are default values. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18259) camel-fhir: Document and test the FHIR consumer
[ https://issues.apache.org/jira/browse/CAMEL-18259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18259: Fix Version/s: 3.x (was: 3.19.0) > camel-fhir: Document and test the FHIR consumer > --- > > Key: CAMEL-18259 > URL: https://issues.apache.org/jira/browse/CAMEL-18259 > Project: Camel > Issue Type: Improvement > Components: camel-fhir >Reporter: James Netherton >Priority: Minor > Fix For: 3.x > > > The FHIR component has a polling consumer where it can do polling operations > against a FHIR server. Seems we have no documentation or tests for this > though, so it'd be useful to add some. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18243) [DOCS] Kafka component - multiple options need updates
[
https://issues.apache.org/jira/browse/CAMEL-18243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18243:
Fix Version/s: 3.19.0
> [DOCS] Kafka component - multiple options need updates
> --
>
> Key: CAMEL-18243
> URL: https://issues.apache.org/jira/browse/CAMEL-18243
> Project: Camel
> Issue Type: Task
> Components: camel-kafka
>Affects Versions: 3.14.0
>Reporter: Mario Majernik
>Priority: Minor
> Fix For: 3.19.0
>
>
> * Option *maxBlockMs* contains description:
> ** {code:java}
> The configuration controls how long sending to kafka will block. These
> methods can be blocked for multiple reasons.{code}
> ** `to kafka will block` -> what
> ** `These methods` -> what methods?
> ** Looks like the first sentence is not finished or there should be one more.
> ** docs:
> [https://camel.apache.org/components/3.14.x/kafka-component.html#_component_option_maxBlockMs]
> * Options *metricsSampleWindowMs* and *noOfMetricsSample* have exactly the
> same description.
> **
> [https://camel.apache.org/components/3.14.x/kafka-component.html#_component_option_metricsSampleWindowMs]
> **
> [https://camel.apache.org/components/3.14.x/kafka-component.html#_component_option_noOfMetricsSample]
> * [PROPOSITION] Option *requestRequiredAcks* have a very long description.
> Would be much more readable if the options will be described in the bullet
> list (acks=-1, acks=0, acks=1, acks=all)
> **
> [https://camel.apache.org/components/3.14.x/kafka-component.html#_component_option_requestRequiredAcks]
> * Option *kerberosPrincipalToLocalRules* contains sentence:
> **
> {code:java}
> For more details on the format please see the security authorization and acls
> documentation.. Multiple values can be separated by a comma. {code}
> but there are no links to the mentioned documentations.
> **
> [https://camel.apache.org/components/3.14.x/kafka-component.html#_component_option_kerberosPrincipalToLocalRules]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18244) [DOCS] AWS SQS component - code samples needs to be updated
[ https://issues.apache.org/jira/browse/CAMEL-18244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18244: Fix Version/s: 3.19.0 > [DOCS] AWS SQS component - code samples needs to be updated > --- > > Key: CAMEL-18244 > URL: https://issues.apache.org/jira/browse/CAMEL-18244 > Project: Camel > Issue Type: Task > Components: camel-aws2 >Affects Versions: 3.14.0 >Reporter: Lucia Drozdová >Priority: Minor > Fix For: 3.19.0 > > > The code samples for Advanced AmazonSQS Configuration and Creating or > updating an SQS queue needs to be fixed: > * the code sample *Advanced AmazonSQS Configuration* is only a sample for > sending messages: > ** > [https://camel.apache.org/components/3.14.x/aws2-sqs-component.html#_advanced_amazonsqs_configuration] > * we fixed the code sample for *Creating or updating an SQS,* but it is > needed to come out with better example > ** > https://camel.apache.org/components/3.14.x/aws2-sqs-component.html#_creating_or_updating_an_sqs_queue > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18241) [DOCS] HTTP component - missing sample
[
https://issues.apache.org/jira/browse/CAMEL-18241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18241:
Fix Version/s: 3.19.0
> [DOCS] HTTP component - missing sample
> --
>
> Key: CAMEL-18241
> URL: https://issues.apache.org/jira/browse/CAMEL-18241
> Project: Camel
> Issue Type: Task
> Components: camel-http
>Affects Versions: 3.14.0
>Reporter: Mario Majernik
>Priority: Minor
> Fix For: 3.19.0
>
>
> Docs:
> [https://access.redhat.com/webassets/avalon/d/red_hat_integration/2022.q2/apache-camel-3.14-doc/components/3.14.x/http-component.html#_response_code]
> Last sentence of chapter:
> {code:java}
> There is a sample below demonstrating this. {code}
> but there is no sample in the docs regarding this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18240) [DOCS] FHIR component - documentation issues
[
https://issues.apache.org/jira/browse/CAMEL-18240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18240:
Fix Version/s: 3.19.0
> [DOCS] FHIR component - documentation issues
>
>
> Key: CAMEL-18240
> URL: https://issues.apache.org/jira/browse/CAMEL-18240
> Project: Camel
> Issue Type: Task
> Components: camel-fhir
>Affects Versions: 3.14.0
>Reporter: Mario Majernik
>Priority: Minor
> Fix For: 3.19.0
>
>
> * Api *operation* contains incomplete URL in the description:
> ** {code:java}
> API for extended FHIR operations https://www{code}
> ** Docs:
> https://camel.apache.org/components/3.14.x/fhir-component.html#_api_parameters_13_apis
> * [PROPOSITION] Each API method contains method signatures. They are shown
> as one long string which is not readable very well. I.E.
> **
> {code:java}
> org.hl7.fhir.instance.model.api.IBaseResource
> resourceByUrl(Class resource,
> org.hl7.fhir.instance.model.api.IIdType iUrl, String ifVersionMatches,
> Boolean returnNull, org.hl7.fhir.instance.model.api.IBaseResource
> returnResource, Boolean throwError,
> java.util.Map
> extraParameters); {code}
> Would be much more readable if each parameter would be on separate line:
> *
> **
> {code:java}
> org.hl7.fhir.instance.model.api.IBaseResource
> resourceByUrl(Class resource,
> org.hl7.fhir.instance.model.api.IIdType iUrl,
> String ifVersionMatches,
> Boolean returnNull,
> org.hl7.fhir.instance.model.api.IBaseResource returnResource,
> Boolean throwError,
> java.util.Map
> extraParameters); {code}
> * APIs read, update, validate - their methods are missing descriptions at all
> ** i.e.:
> [https://camel.apache.org/components/3.14.x/fhir-component.html#_api_validate]
> * All API operation's methods - Alias column is always empty --> could be
> erased from tables.
> ** i.e. method resource and its table:
> ***
> https://camel.apache.org/components/3.14.x/fhir-component.html#_api_validate
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18240) [DOCS] FHIR component - documentation issues
[
https://issues.apache.org/jira/browse/CAMEL-18240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17599949#comment-17599949
]
Claus Ibsen commented on CAMEL-18240:
-
We scrape the docs from javadoc / source code and if fhir does not provide any
then there is nothing to show
> [DOCS] FHIR component - documentation issues
>
>
> Key: CAMEL-18240
> URL: https://issues.apache.org/jira/browse/CAMEL-18240
> Project: Camel
> Issue Type: Task
> Components: camel-fhir
>Affects Versions: 3.14.0
>Reporter: Mario Majernik
>Priority: Minor
>
> * Api *operation* contains incomplete URL in the description:
> ** {code:java}
> API for extended FHIR operations https://www{code}
> ** Docs:
> https://camel.apache.org/components/3.14.x/fhir-component.html#_api_parameters_13_apis
> * [PROPOSITION] Each API method contains method signatures. They are shown
> as one long string which is not readable very well. I.E.
> **
> {code:java}
> org.hl7.fhir.instance.model.api.IBaseResource
> resourceByUrl(Class resource,
> org.hl7.fhir.instance.model.api.IIdType iUrl, String ifVersionMatches,
> Boolean returnNull, org.hl7.fhir.instance.model.api.IBaseResource
> returnResource, Boolean throwError,
> java.util.Map
> extraParameters); {code}
> Would be much more readable if each parameter would be on separate line:
> *
> **
> {code:java}
> org.hl7.fhir.instance.model.api.IBaseResource
> resourceByUrl(Class resource,
> org.hl7.fhir.instance.model.api.IIdType iUrl,
> String ifVersionMatches,
> Boolean returnNull,
> org.hl7.fhir.instance.model.api.IBaseResource returnResource,
> Boolean throwError,
> java.util.Map
> extraParameters); {code}
> * APIs read, update, validate - their methods are missing descriptions at all
> ** i.e.:
> [https://camel.apache.org/components/3.14.x/fhir-component.html#_api_validate]
> * All API operation's methods - Alias column is always empty --> could be
> erased from tables.
> ** i.e. method resource and its table:
> ***
> https://camel.apache.org/components/3.14.x/fhir-component.html#_api_validate
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18238) camel-jbang - Used configmaps/secrets should captured
[ https://issues.apache.org/jira/browse/CAMEL-18238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18238: Fix Version/s: 3.x (was: 3.19.0) > camel-jbang - Used configmaps/secrets should captured > - > > Key: CAMEL-18238 > URL: https://issues.apache.org/jira/browse/CAMEL-18238 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.x > > > With CAMEL-18171 then when using configmap or secret then we should capture > these names so we know what are in use. > This can aid for deployment which allows us to generate manifest files that > refer to the used cm/secrets so k8s can mount these automatic. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18239) [DOCS] Bean components - missing examples
[
https://issues.apache.org/jira/browse/CAMEL-18239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18239:
Fix Version/s: 3.19.0
> [DOCS] Bean components - missing examples
> -
>
> Key: CAMEL-18239
> URL: https://issues.apache.org/jira/browse/CAMEL-18239
> Project: Camel
> Issue Type: Task
> Components: camel-bean
>Affects Versions: 3.14.0
>Reporter: Mario Majernik
>Priority: Minor
> Fix For: 3.19.0
>
>
> Docs: [https://camel.apache.org/components/3.14.x/bean-component.html#_using]
> Missing java code example after:
> {code:java}
> You can use the createProxy() methods on ProxyHelper to create a proxy that
> will generate exchanges and send them to any endpoint:{code}
> Similar next chapter in docs:
> [https://camel.apache.org/components/3.14.x/bean-component.html#_bean_as_endpoint]
> Missing code examples after the first and third sentence:
> *
> {code:java}
> In the route below:{code}
> *
> {code:java}
> The source for the bean is just a plain POJO:{code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18239) [DOCS] Bean components - missing examples
[
https://issues.apache.org/jira/browse/CAMEL-18239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18239:
Component/s: documentation
(was: camel-bean)
> [DOCS] Bean components - missing examples
> -
>
> Key: CAMEL-18239
> URL: https://issues.apache.org/jira/browse/CAMEL-18239
> Project: Camel
> Issue Type: Task
> Components: documentation
>Affects Versions: 3.14.0
>Reporter: Mario Majernik
>Priority: Minor
> Fix For: 3.19.0
>
>
> Docs: [https://camel.apache.org/components/3.14.x/bean-component.html#_using]
> Missing java code example after:
> {code:java}
> You can use the createProxy() methods on ProxyHelper to create a proxy that
> will generate exchanges and send them to any endpoint:{code}
> Similar next chapter in docs:
> [https://camel.apache.org/components/3.14.x/bean-component.html#_bean_as_endpoint]
> Missing code examples after the first and third sentence:
> *
> {code:java}
> In the route below:{code}
> *
> {code:java}
> The source for the bean is just a plain POJO:{code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18238) camel-jbang - Used configmaps/secrets should captured
[ https://issues.apache.org/jira/browse/CAMEL-18238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18238: Priority: Minor (was: Major) > camel-jbang - Used configmaps/secrets should captured > - > > Key: CAMEL-18238 > URL: https://issues.apache.org/jira/browse/CAMEL-18238 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.x > > > With CAMEL-18171 then when using configmap or secret then we should capture > these names so we know what are in use. > This can aid for deployment which allows us to generate manifest files that > refer to the used cm/secrets so k8s can mount these automatic. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18236) camel-karaf - camel property not resolved
[
https://issues.apache.org/jira/browse/CAMEL-18236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-18236.
-
Resolution: Information Provided
> camel-karaf - camel property not resolved
> -
>
> Key: CAMEL-18236
> URL: https://issues.apache.org/jira/browse/CAMEL-18236
> Project: Camel
> Issue Type: Bug
>Affects Versions: 3.15.0
> Environment: {code:java}
> {code}
>Reporter: Vincent
>Priority: Minor
>
> Hi,
>
> I have a strange comportement with camel and beans containing properties.
>
> I have a route "SimpleRoute" in which a configurable processor is injected
> "FakeProcessor" :
>
>
> {code:java}
> @Named
> public class SimpleRoute extends RouteBuilder {
> private final FakeProcessor fakeProcessor;
> @Inject
> public SimpleRoute(FakeProcessor fakeProcessor) {
> this.fakeProcessor = fakeProcessor;
> }
> @Override
> public void configure() throws Exception {
> from("direct:input")
> .process(fakeProcessor)
> .log("Input processed");
> }
> }{code}
>
> {code:java}
> @Named("fakeProcessor")
> @Singleton
> public class FakeProcessor implements Processor {
> private String property;
> @Inject
> public FakeProcessor(@ConfigProperty("${configuration.path}") String
> property) {
> this.property = property;
> }
> @Override
> public void process(Exchange exchange) throws Exception { }
> }{code}
> {code:java}
> @Named("fakeProcessor2")
> @Singleton public class FakeProcessor2 implements Processor {
> private String property;
>
> @Inject
> public FakeProcessor2(@ConfigProperty("${configuration.path}") String
> property) { this.property = property; }
>
> @Override
> public void process(Exchange exchange) throws Exception { }
> }
> {code}
> The property "${configuration.path}" is interpreted in bean FakeProcessor2
> but not in bean FakeProcessor (which is injected to my route).
>
> Here is the blueprint file :
>
> {code:java}
>
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xmlns:camel="http://camel.apache.org/schema/blueprint;
>
> xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
> xsi:schemaLocation="
> http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
> persistent-id="voo.esb.services.contactoccurence.sendemail">
>
>
> value="ContactOccurenceSendEmail"/>
> value="${karaf.base}/etc/voo.esb.services.contactoccurence.sendemail.yml"/>
>
>
> trace="{{camel.context.trace}}" autoStartup="true">
> location="blueprint:voo.esb.services.contactoccurence.sendemail"/>->
>
>
>
> class="be.voo.esb.services.contactoccurence.sendemail.processor.FakeProcessor">
>
>
> class="be.voo.esb.services.contactoccurence.sendemail.processor.FakeProcessor2">
>
>
> class="be.voo.esb.services.contactoccurence.sendemail.SimpleRoute"
> scope="prototype">
>
>
> {code}
>
> Do you have any ideas?
>
> Thank you for your help!
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18235) camel-aws-s3 - Should autoCreateBucket be true or false by default
[ https://issues.apache.org/jira/browse/CAMEL-18235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18235: Priority: Minor (was: Major) > camel-aws-s3 - Should autoCreateBucket be true or false by default > -- > > Key: CAMEL-18235 > URL: https://issues.apache.org/jira/browse/CAMEL-18235 > Project: Camel > Issue Type: Improvement > Components: camel-aws >Reporter: Claus Ibsen >Priority: Minor > Fix For: 3.x > > > some of the other components in camel-google or camel-minio seems to have it > as true, but s3 is false. > Noticed this in this PR > https://github.com/apache/camel/pull/7901 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18234) Exception building aws2-sqs route when certificate validation is disabled and a proxy is configured
[
https://issues.apache.org/jira/browse/CAMEL-18234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18234:
Fix Version/s: 3.x
> Exception building aws2-sqs route when certificate validation is disabled and
> a proxy is configured
> ---
>
> Key: CAMEL-18234
> URL: https://issues.apache.org/jira/browse/CAMEL-18234
> Project: Camel
> Issue Type: Bug
> Components: camel-aws2
>Affects Versions: 3.17.0
> Environment: Camel 3.17.0 / Spring Boot 2.6.7 / OpenJDK 64-bit Server
> VM 18.0.1.1+2
>Reporter: Dylan Piergies
>Priority: Minor
> Fix For: 3.x
>
>
> An aws2-sqs route fails to configure in Camel/Spring Boot when the
> camel.component.aws2-sqs.trust-all-certificates Spring property is set to
> true and a proxy is configured.
> Consider route:
> {{@Component}}
> {{public class SqsRoute extends EndpointRouteBuilder {}}
> {{ @Override}}
> {{ public void configure() throws Exception {}}
> {{ from(aws2Sqs("srcQueue"))}}
> {{ .to(aws2Sqs("dstQueue"));}}
> {{ }}}
> {{}}}
> And in application.yml:
> {{camel:}}
> {{ component:}}
> {{ aws2-sqs:}}
> {{ use-default-credentials-provider: true}}
> {{ proxy-protocol: http}}
> {{ proxy-host: localhost}}
> {{ proxy-port: 8118}}
> {{ trust-all-certificates: true}}
> {{ springboot:}}
> {{ main-run-controller: true}}
> Exception is thrown:
> {{org.apache.camel.FailedToCreateRouteException: Failed to create route
> route1: Route(route1)[From[aws2-sqs://srcQueue] -> [To[aws2-sqs://ds...
> because of Failed to resolve endpoint: aws2-sqs://srcQueue due to: The
> httpClient and the httpClientBuilder can't both be configured.}}
> {{ at
> org.apache.camel.reifier.RouteReifier.createRoute(RouteReifier.java:80)
> ~[camel-core-reifier-3.16.0.jar:3.16.0]}}
> {{ at
> org.apache.camel.impl.DefaultModelReifierFactory.createRoute(DefaultModelReifierFactory.java:49)
> ~[camel-core-engine-3.16.0.jar:3.16.0]}}
> {{ at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:887)
> ~[camel-core-engine-3.16.0.jar:3.16.0]}}
> {{ at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:775)
> ~[camel-core-engine-3.16.0.jar:3.16.0]}}
> {{ at
> org.apache.camel.impl.engine.AbstractCamelContext.doInit(AbstractCamelContext.java:2937)
> ~[camel-base-engine-3.16.0.jar:3.16.0]}}
> {{ at
> org.apache.camel.support.service.BaseService.init(BaseService.java:83)
> ~[camel-api-3.16.0.jar:3.16.0]}}
> {{ at
> org.apache.camel.impl.engine.AbstractCamelContext.init(AbstractCamelContext.java:2620)
> ~[camel-base-engine-3.16.0.jar:3.16.0]}}
> {{ at
> org.apache.camel.support.service.BaseService.start(BaseService.java:111)
> ~[camel-api-3.16.0.jar:3.16.0]}}
> {{ at
> org.apache.camel.impl.engine.AbstractCamelContext.start(AbstractCamelContext.java:2639)
> ~[camel-base-engine-3.16.0.jar:3.16.0]}}
> {{ at
> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:255)
> ~[camel-core-engine-3.16.0.jar:3.16.0]}}
> {{ at
> org.apache.camel.spring.SpringCamelContext.start(SpringCamelContext.java:119)
> ~[camel-spring-3.16.0.jar:3.16.0]}}
> {{ at
> org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:151)
> ~[camel-spring-3.16.0.jar:3.16.0]}}
> {{ at
> org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:176)
> ~[spring-context-5.3.19.jar:5.3.19]}}
> {{ at
> org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:169)
> ~[spring-context-5.3.19.jar:5.3.19]}}
> {{ at
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:143)
> ~[spring-context-5.3.19.jar:5.3.19]}}
> {{ at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:421)
> ~[spring-context-5.3.19.jar:5.3.19]}}
> {{ at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:378)
> ~[spring-context-5.3.19.jar:5.3.19]}}
> {{ at
> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:938)
> ~[spring-context-5.3.19.jar:5.3.19]}}
> {{ at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:586)
> ~[spring-context-5.3.19.jar:5.3.19]}}
> {{ at
> org.springframework.boot.SpringApplication.refresh(SpringApplication.java:740)
> ~[spring-boot-2.6.7.jar:2.6.7]}}
> {{ at
>
[jira] [Resolved] (CAMEL-18181) Build does not work on Windows
[ https://issues.apache.org/jira/browse/CAMEL-18181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18181. - Resolution: Information Provided > Build does not work on Windows > -- > > Key: CAMEL-18181 > URL: https://issues.apache.org/jira/browse/CAMEL-18181 > Project: Camel > Issue Type: Task > Components: build system >Affects Versions: 3.17.0 >Reporter: Otavio Rodolfo Piske >Priority: Minor > > It fails with: > > ``` > Error: Failed to execute goal > org.apache.camel:camel-package-maven-plugin:3.18.0-SNAPSHOT:generate > (generate) on project camel-core-engine: Error generating data > org.apache.maven.plugin.MojoExecutionException: Error reading file > D:\a\camel\camel\core\camel-core-engine\src\main\docs\modules\eips\pages\aggregate-eip.adoc > Reason: org.apache.maven.plugin.MojoFailureException: File > D:\a\camel\camel\core\camel-core-engine\src\main\docs\modules\eips\pages\aggregate-eip.adoc > has unexpected structure with no empty line. -> [Help 1] > ``` -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18186) camel-saga: tracing information is not propagate on compensation/completion
[
https://issues.apache.org/jira/browse/CAMEL-18186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18186:
Fix Version/s: 3.x
> camel-saga: tracing information is not propagate on compensation/completion
>
>
> Key: CAMEL-18186
> URL: https://issues.apache.org/jira/browse/CAMEL-18186
> Project: Camel
> Issue Type: Improvement
> Components: eip
>Affects Versions: 3.11.7
>Reporter: chio chuan ooi
>Priority: Minor
> Fix For: 3.x
>
>
> When saga coordinator finalize the step, new exchange is being created, all
> the tracing information in the previous exchange is not being propagated to
> the new exchange and causing new trace is being generated.
>
> {code:java}
> private Exchange createExchange(Endpoint endpoint, CamelSagaStep step) {
> Exchange exchange = endpoint.createExchange();
> exchange.getIn().setHeader(Exchange.SAGA_LONG_RUNNING_ACTION,
> getId());
> Map values = optionValues.get(step);
> if (values != null) {
> for (Map.Entry entry : values.entrySet()) {
> exchange.getIn().setHeader(entry.getKey(), entry.getValue());
> }
> }
> return exchange;
> } {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18181) Build does not work on Windows
[ https://issues.apache.org/jira/browse/CAMEL-18181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18181: Priority: Minor (was: Major) > Build does not work on Windows > -- > > Key: CAMEL-18181 > URL: https://issues.apache.org/jira/browse/CAMEL-18181 > Project: Camel > Issue Type: Task > Components: build system >Affects Versions: 3.17.0 >Reporter: Otavio Rodolfo Piske >Priority: Minor > > It fails with: > > ``` > Error: Failed to execute goal > org.apache.camel:camel-package-maven-plugin:3.18.0-SNAPSHOT:generate > (generate) on project camel-core-engine: Error generating data > org.apache.maven.plugin.MojoExecutionException: Error reading file > D:\a\camel\camel\core\camel-core-engine\src\main\docs\modules\eips\pages\aggregate-eip.adoc > Reason: org.apache.maven.plugin.MojoFailureException: File > D:\a\camel\camel\core\camel-core-engine\src\main\docs\modules\eips\pages\aggregate-eip.adoc > has unexpected structure with no empty line. -> [Help 1] > ``` -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18181) Build does not work on Windows
[ https://issues.apache.org/jira/browse/CAMEL-18181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17599946#comment-17599946 ] Claus Ibsen commented on CAMEL-18181: - You can skip building the docs I think there is a profile for that, try with -P fastinstall > Build does not work on Windows > -- > > Key: CAMEL-18181 > URL: https://issues.apache.org/jira/browse/CAMEL-18181 > Project: Camel > Issue Type: Task > Components: build system >Affects Versions: 3.17.0 >Reporter: Otavio Rodolfo Piske >Priority: Minor > > It fails with: > > ``` > Error: Failed to execute goal > org.apache.camel:camel-package-maven-plugin:3.18.0-SNAPSHOT:generate > (generate) on project camel-core-engine: Error generating data > org.apache.maven.plugin.MojoExecutionException: Error reading file > D:\a\camel\camel\core\camel-core-engine\src\main\docs\modules\eips\pages\aggregate-eip.adoc > Reason: org.apache.maven.plugin.MojoFailureException: File > D:\a\camel\camel\core\camel-core-engine\src\main\docs\modules\eips\pages\aggregate-eip.adoc > has unexpected structure with no empty line. -> [Help 1] > ``` -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18180) Force LF endings in .adoc files
[
https://issues.apache.org/jira/browse/CAMEL-18180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18180:
Fix Version/s: (was: 3.19.0)
> Force LF endings in .adoc files
> ---
>
> Key: CAMEL-18180
> URL: https://issues.apache.org/jira/browse/CAMEL-18180
> Project: Camel
> Issue Type: Task
> Components: build system
>Reporter: Rafał Gała
>Priority: Minor
>
> Please consider adding the
> {noformat}
> *.adoc text eol=lf{noformat}
> in .gitattributes to force LF line endings in .adoc files to avoid issues
> with
> {code:java}
> String[] lines = text.split("\n"); {code}
> in *UpdateReadmeMojo* class when a git checkout was made on a Windows machine
> with GIT configuration set to {*}autocrlf = true{*}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18180) Force LF endings in .adoc files
[
https://issues.apache.org/jira/browse/CAMEL-18180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-18180.
-
Fix Version/s: 3.x
Resolution: Fixed
> Force LF endings in .adoc files
> ---
>
> Key: CAMEL-18180
> URL: https://issues.apache.org/jira/browse/CAMEL-18180
> Project: Camel
> Issue Type: Task
> Components: build system
>Reporter: Rafał Gała
>Priority: Minor
> Fix For: 3.x
>
>
> Please consider adding the
> {noformat}
> *.adoc text eol=lf{noformat}
> in .gitattributes to force LF line endings in .adoc files to avoid issues
> with
> {code:java}
> String[] lines = text.split("\n"); {code}
> in *UpdateReadmeMojo* class when a git checkout was made on a Windows machine
> with GIT configuration set to {*}autocrlf = true{*}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18177) camel-slack - Honour Retry-After when requests are rate-limited
[
https://issues.apache.org/jira/browse/CAMEL-18177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18177:
Priority: Major (was: Minor)
> camel-slack - Honour Retry-After when requests are rate-limited
> ---
>
> Key: CAMEL-18177
> URL: https://issues.apache.org/jira/browse/CAMEL-18177
> Project: Camel
> Issue Type: Improvement
> Components: camel-slack
>Reporter: Luca Burgazzoli
>Priority: Major
> Fix For: 3.x
>
>
> According to slack's doc:
> {code}
> If you exceed a rate limit when using any of our HTTP-based APIs (including
> Incoming Webhooks), Slack will return a HTTP 429 Too Many Requests error, and
> a Retry-After HTTP header containing the number of seconds until you can
> retry.
> {code}
> We should explore if we can honor the Retry-After seconds to perform the
> next poll.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18180) Force LF endings in .adoc files
[
https://issues.apache.org/jira/browse/CAMEL-18180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18180:
Fix Version/s: 3.19.0
> Force LF endings in .adoc files
> ---
>
> Key: CAMEL-18180
> URL: https://issues.apache.org/jira/browse/CAMEL-18180
> Project: Camel
> Issue Type: Task
> Components: build system
>Reporter: Rafał Gała
>Priority: Minor
> Fix For: 3.19.0
>
>
> Please consider adding the
> {noformat}
> *.adoc text eol=lf{noformat}
> in .gitattributes to force LF line endings in .adoc files to avoid issues
> with
> {code:java}
> String[] lines = text.split("\n"); {code}
> in *UpdateReadmeMojo* class when a git checkout was made on a Windows machine
> with GIT configuration set to {*}autocrlf = true{*}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18177) camel-slack - Honour Retry-After when requests are rate-limited
[
https://issues.apache.org/jira/browse/CAMEL-18177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17599945#comment-17599945
]
Claus Ibsen commented on CAMEL-18177:
-
Ah yeah if the consumer is scheduled we could maybe grab that seconds and then
store that in some state and then skip the poll if still reminding seconds left
- then we can have some kind of method a component can implement that can
support grabbing this rate limit until header
> camel-slack - Honour Retry-After when requests are rate-limited
> ---
>
> Key: CAMEL-18177
> URL: https://issues.apache.org/jira/browse/CAMEL-18177
> Project: Camel
> Issue Type: Improvement
> Components: camel-slack
>Reporter: Luca Burgazzoli
>Priority: Minor
> Fix For: 3.x
>
>
> According to slack's doc:
> {code}
> If you exceed a rate limit when using any of our HTTP-based APIs (including
> Incoming Webhooks), Slack will return a HTTP 429 Too Many Requests error, and
> a Retry-After HTTP header containing the number of seconds until you can
> retry.
> {code}
> We should explore if we can honor the Retry-After seconds to perform the
> next poll.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-18164) camel-spring-boot - Add platform-http-starter
[ https://issues.apache.org/jira/browse/CAMEL-18164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-18164: --- Assignee: (was: Claus Ibsen) > camel-spring-boot - Add platform-http-starter > - > > Key: CAMEL-18164 > URL: https://issues.apache.org/jira/browse/CAMEL-18164 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.19.0 > > > To make it consistent with camel-jbang to run on either spring boot or > quarkus then it would be good to have a starter for platform-http. > We can try to hook into the spring http server and if we can't find a general > way we may need to assume its based on tomcat / servlet. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18164) camel-spring-boot - Add platform-http-starter
[ https://issues.apache.org/jira/browse/CAMEL-18164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18164. - Resolution: Duplicate > camel-spring-boot - Add platform-http-starter > - > > Key: CAMEL-18164 > URL: https://issues.apache.org/jira/browse/CAMEL-18164 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.19.0 > > > To make it consistent with camel-jbang to run on either spring boot or > quarkus then it would be good to have a starter for platform-http. > We can try to hook into the spring http server and if we can't find a general > way we may need to assume its based on tomcat / servlet. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18155) camel-jbang - Display sub commands by default
[ https://issues.apache.org/jira/browse/CAMEL-18155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18155. - Fix Version/s: 3.19.0 (was: 3.x) Resolution: Fixed > camel-jbang - Display sub commands by default > - > > Key: CAMEL-18155 > URL: https://issues.apache.org/jira/browse/CAMEL-18155 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Priority: Minor > Fix For: 3.19.0 > > > if you run > camel build > then it has a number of sub commands, but you cant seem them, you have to run > camel build --help > lets see if we can show the sub commands when you just run > camel build -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18158) camel-netty-http: investigate using HeaderFilterStrategy
[ https://issues.apache.org/jira/browse/CAMEL-18158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18158: Fix Version/s: 3.x > camel-netty-http: investigate using HeaderFilterStrategy > > > Key: CAMEL-18158 > URL: https://issues.apache.org/jira/browse/CAMEL-18158 > Project: Camel > Issue Type: Task > Components: camel-netty-http >Reporter: Otavio Rodolfo Piske >Priority: Minor > Fix For: 3.x > > > Based on a suggestion from Claus in this PR: > [https://github.com/apache/camel/pull/7694#pullrequestreview-990818819] > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18158) camel-netty-http: investigate using HeaderFilterStrategy
[ https://issues.apache.org/jira/browse/CAMEL-18158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18158: Priority: Minor (was: Major) > camel-netty-http: investigate using HeaderFilterStrategy > > > Key: CAMEL-18158 > URL: https://issues.apache.org/jira/browse/CAMEL-18158 > Project: Camel > Issue Type: Task > Components: camel-netty-http >Reporter: Otavio Rodolfo Piske >Priority: Minor > > Based on a suggestion from Claus in this PR: > [https://github.com/apache/camel/pull/7694#pullrequestreview-990818819] > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18143) Autowire quartz scheduler in quartz component
[ https://issues.apache.org/jira/browse/CAMEL-18143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18143: Fix Version/s: 3.19.0 (was: 3.x) > Autowire quartz scheduler in quartz component > - > > Key: CAMEL-18143 > URL: https://issues.apache.org/jira/browse/CAMEL-18143 > Project: Camel > Issue Type: Improvement > Components: camel-quartz >Affects Versions: 3.17.0 >Reporter: Joe Siponen >Priority: Minor > Fix For: 3.19.0 > > > I suggest that the [scheduler > option|https://camel.apache.org/components/3.17.x/quartz-component.html#_component_options] > is autowired for the quartz component. > The instructions for the QUARKUS BASED configuration of the quartz-component > seems to (implicitly) assume that it is: > [https://camel.apache.org/camel-quarkus/2.7.x/reference/extensions/quartz.html] > However, the documentation does not mark scheduler as being autowired so the > quarkus based documentation is not correct as it leaves out the part required > for wiring the quarkus provided scheduler with camel's quartz component. > However, one could argue that the sceduler should be autowired in order to > reduce the necessity for boilerplate code when there is clear candidate for > autowiring. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18140) camel-jbang - Add support for jitpack dependencies
[ https://issues.apache.org/jira/browse/CAMEL-18140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18140: Priority: Minor (was: Major) > camel-jbang - Add support for jitpack dependencies > -- > > Key: CAMEL-18140 > URL: https://issues.apache.org/jira/browse/CAMEL-18140 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Priority: Minor > Fix For: 3.x > > > Lets see if we can resolve dependencies using jitpack style > https://camel.apache.org/camel-k/1.9.x/configuration/dependencies.html#dependencies-kind-jitpack -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18131) camel-health - Add health checks for components that has extension for connectivity verification
[ https://issues.apache.org/jira/browse/CAMEL-18131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17599942#comment-17599942 ] Claus Ibsen commented on CAMEL-18131: - Thanka Rhuan, you are welcome to work on more health checks > camel-health - Add health checks for components that has extension for > connectivity verification > > > Key: CAMEL-18131 > URL: https://issues.apache.org/jira/browse/CAMEL-18131 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Assignee: Rhuan Rocha >Priority: Major > Fix For: 3.19.0 > > > A number of components have the old component extension verification (see > aws-s3) - we can migrate that into health-checks. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18121) camel-kafka - Upgrade to Kafka clients 3.2.x
[ https://issues.apache.org/jira/browse/CAMEL-18121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17599941#comment-17599941 ] Claus Ibsen commented on CAMEL-18121: - quarkus is on 3.2.1 > camel-kafka - Upgrade to Kafka clients 3.2.x > > > Key: CAMEL-18121 > URL: https://issues.apache.org/jira/browse/CAMEL-18121 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-kafka >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18121) camel-kafka - Upgrade to Kafka clients 3.2.x
[ https://issues.apache.org/jira/browse/CAMEL-18121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17599940#comment-17599940 ] Claus Ibsen commented on CAMEL-18121: - spring boot is still on 3.1.x > camel-kafka - Upgrade to Kafka clients 3.2.x > > > Key: CAMEL-18121 > URL: https://issues.apache.org/jira/browse/CAMEL-18121 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-kafka >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18121) camel-kafka - Upgrade to Kafka clients 3.2.x
[ https://issues.apache.org/jira/browse/CAMEL-18121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17599940#comment-17599940 ] Claus Ibsen edited comment on CAMEL-18121 at 9/3/22 2:38 PM: - spring boot is still on 3.1.x however kafka are backwards compatible was (Author: davsclaus): spring boot is still on 3.1.x > camel-kafka - Upgrade to Kafka clients 3.2.x > > > Key: CAMEL-18121 > URL: https://issues.apache.org/jira/browse/CAMEL-18121 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-kafka >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18121) camel-kafka - Upgrade to Kafka clients 3.2.x
[ https://issues.apache.org/jira/browse/CAMEL-18121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18121: Fix Version/s: 3.19.0 (was: 3.x) > camel-kafka - Upgrade to Kafka clients 3.2.x > > > Key: CAMEL-18121 > URL: https://issues.apache.org/jira/browse/CAMEL-18121 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-kafka >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18120) camel-jbang - The openapi generator should support generating POJOs
[ https://issues.apache.org/jira/browse/CAMEL-18120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18120: Fix Version/s: 3.x (was: 3.19.0) > camel-jbang - The openapi generator should support generating POJOs > --- > > Key: CAMEL-18120 > URL: https://issues.apache.org/jira/browse/CAMEL-18120 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.x > > > It would be good to allow generating POJOs so we can have rest-dsl auto map > to these. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-17823) UUID generator in the Simple language
[
https://issues.apache.org/jira/browse/CAMEL-17823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-17823.
-
Resolution: Fixed
There is a new uuid function now
> UUID generator in the Simple language
> -
>
> Key: CAMEL-17823
> URL: https://issues.apache.org/jira/browse/CAMEL-17823
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Affects Versions: 3.15.0
>Reporter: Raymond
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.19.0
>
>
> One common use case I see a lot is to set a unique ID (UUID). There are
> several ways to do this. For example:
> 1) Reuse a Camel generated id (exchangeid, breadcrumbid, messageid). For
> example: ${exchangeId}
> 2) Use 'generate-id' function in XSLT on a node-set
> ([https://www.w3schools.com/xml/func_generateid.asp)]
> 3) Create bean (and create UUID directly in Java) or with help of the
> UUIDGenerator ([https://camel.apache.org/manual/uuidgenerator.html)].
> 4) Create a Groovy expression
> I think, however, it would be more convenient and easier for users to have a
> function directly within the Simple language. Something like:
> generate-id(type)
> Where type is one of "Classic, Default, Short, Simple". When none is used,
> the default should be used.
> Source:
>
> [https://camel.apache.org/manual/uuidgenerator.html|https://camel.apache.org/manual/uuidgenerator.html)]
> [https://www.designingbuildings.co.uk/wiki/Global_Unique_IDs_(GUIDs)]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-17823) UUID generator in the Simple language
[
https://issues.apache.org/jira/browse/CAMEL-17823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-17823:
---
Assignee: Claus Ibsen
> UUID generator in the Simple language
> -
>
> Key: CAMEL-17823
> URL: https://issues.apache.org/jira/browse/CAMEL-17823
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Affects Versions: 3.15.0
>Reporter: Raymond
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.19.0
>
>
> One common use case I see a lot is to set a unique ID (UUID). There are
> several ways to do this. For example:
> 1) Reuse a Camel generated id (exchangeid, breadcrumbid, messageid). For
> example: ${exchangeId}
> 2) Use 'generate-id' function in XSLT on a node-set
> ([https://www.w3schools.com/xml/func_generateid.asp)]
> 3) Create bean (and create UUID directly in Java) or with help of the
> UUIDGenerator ([https://camel.apache.org/manual/uuidgenerator.html)].
> 4) Create a Groovy expression
> I think, however, it would be more convenient and easier for users to have a
> function directly within the Simple language. Something like:
> generate-id(type)
> Where type is one of "Classic, Default, Short, Simple". When none is used,
> the default should be used.
> Source:
>
> [https://camel.apache.org/manual/uuidgenerator.html|https://camel.apache.org/manual/uuidgenerator.html)]
> [https://www.designingbuildings.co.uk/wiki/Global_Unique_IDs_(GUIDs)]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-17856) camel-jackson - Upgrade to 2.14.x
[ https://issues.apache.org/jira/browse/CAMEL-17856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-17856: Fix Version/s: 3.x (was: 3.19.0) > camel-jackson - Upgrade to 2.14.x > - > > Key: CAMEL-17856 > URL: https://issues.apache.org/jira/browse/CAMEL-17856 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jackson >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.x > > > We should upgrade, but would be good to have it aligned with SB and Quarkus > as well with the version they use. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-17856) camel-jackson - Upgrade to 2.14.x
[ https://issues.apache.org/jira/browse/CAMEL-17856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17599929#comment-17599929 ] Claus Ibsen commented on CAMEL-17856: - quarkus is still on 2.13.x > camel-jackson - Upgrade to 2.14.x > - > > Key: CAMEL-17856 > URL: https://issues.apache.org/jira/browse/CAMEL-17856 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jackson >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.x > > > We should upgrade, but would be good to have it aligned with SB and Quarkus > as well with the version they use. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-17932) camel-spring-boot - EndpointInject happens before CamelContextConfiguration#beforeApplicationStart
[
https://issues.apache.org/jira/browse/CAMEL-17932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-17932:
Summary: camel-spring-boot - EndpointInject happens before
CamelContextConfiguration#beforeApplicationStart (was: EndpointInject happens
before CamelContextConfiguration#beforeApplicationStart)
> camel-spring-boot - EndpointInject happens before
> CamelContextConfiguration#beforeApplicationStart
> --
>
> Key: CAMEL-17932
> URL: https://issues.apache.org/jira/browse/CAMEL-17932
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-boot, tests
>Reporter: John Poth
>Priority: Minor
> Fix For: 3.x
>
>
> Currently something like this fails in camel-spring-boot tests:
> {code:java}
> @EndpointInject("mock:result")
> MockEndpoint mock;
> @Test
> public void testComponentConfigured() {
> // this fails
> assertTrue(mock.isLog());
> }
> @Bean
> CamelContextConfiguration contextConfiguration() {
> return new CamelContextConfiguration() {
> @Override
> public void beforeApplicationStart(CamelContext context) {
> MockComponent mock = new MockComponent(context);
> mock.setLog(true);
> context.addComponent("mock", mock);
> }
> @Override
> public void afterApplicationStart(CamelContext camelContext) {
> //do nothing here
> }
> };
> }
> {code}
> This is because the wiring for *@EndpointInject* happens before
> *CamelContextConfiguration#beforeApplicationStart*. Workaround is to
> configure the component via @Bean
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18462) LTS dates are not well documented in release notes
[ https://issues.apache.org/jira/browse/CAMEL-18462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18462: Priority: Trivial (was: Major) > LTS dates are not well documented in release notes > -- > > Key: CAMEL-18462 > URL: https://issues.apache.org/jira/browse/CAMEL-18462 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Sebb >Priority: Trivial > > The individual release pages for LTS releases (e.g. [1]) don't give a release > date or an EOL date. The release dates are mentioned on the release summary > page [2], however there is no link to this page from the individual release > pages. > It looks like the only documentation for the LTS dates is on the downloads > page [3], but that is not at all obvious, and does not cover recently > superseded releases. For example, what is the EOL for 3.8.0, released in July > 2022?. > It should be easier to find out this information from the releases notes. > For example they could be documented here [2], with backlinks from [1] etc. > [1] https://camel.apache.org/releases/release-3.14.5/ > [2] https://camel.apache.org/releases/ > [3] https://camel.apache.org/download/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18462) LTS dates are not well documented in release notes
[ https://issues.apache.org/jira/browse/CAMEL-18462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17599928#comment-17599928 ] Claus Ibsen commented on CAMEL-18462: - Only LTS releases has an EOL date. Any other release is EOL asap > LTS dates are not well documented in release notes > -- > > Key: CAMEL-18462 > URL: https://issues.apache.org/jira/browse/CAMEL-18462 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Sebb >Priority: Major > > The individual release pages for LTS releases (e.g. [1]) don't give a release > date or an EOL date. The release dates are mentioned on the release summary > page [2], however there is no link to this page from the individual release > pages. > It looks like the only documentation for the LTS dates is on the downloads > page [3], but that is not at all obvious, and does not cover recently > superseded releases. For example, what is the EOL for 3.8.0, released in July > 2022?. > It should be easier to find out this information from the releases notes. > For example they could be documented here [2], with backlinks from [1] etc. > [1] https://camel.apache.org/releases/release-3.14.5/ > [2] https://camel.apache.org/releases/ > [3] https://camel.apache.org/download/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18112) Support trace breakpoint
[ https://issues.apache.org/jira/browse/CAMEL-18112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18112: Fix Version/s: 3.x > Support trace breakpoint > > > Key: CAMEL-18112 > URL: https://issues.apache.org/jira/browse/CAMEL-18112 > Project: Camel > Issue Type: New Feature > Components: tooling >Reporter: Aurélien Pupier >Priority: Minor > Fix For: 3.x > > > it would be nice to support trace breakpoints. > Most IDEs are providing this kind of feature. It allows to provide traces > during a debug session without modifying the source code. > see: > - > https://microsoft.github.io/debug-adapter-protocol/specification#Types_SourceBreakpoint > logMessage > - In IntelliJ, using non-suspended in combination with logging options > https://www.jetbrains.com/help/idea/using-breakpoints.html#suspend_policy > - In Eclipse, Tracepoint > https://www.eclipse.org/community/eclipse_newsletter/2017/june/article1.php > - In VS Code, Logpoint > https://code.visualstudio.com/docs/editor/debugging#_logpoints -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18112) camel-debug - Support trace breakpoint
[ https://issues.apache.org/jira/browse/CAMEL-18112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18112: Summary: camel-debug - Support trace breakpoint (was: Support trace breakpoint) > camel-debug - Support trace breakpoint > -- > > Key: CAMEL-18112 > URL: https://issues.apache.org/jira/browse/CAMEL-18112 > Project: Camel > Issue Type: New Feature > Components: tooling >Reporter: Aurélien Pupier >Priority: Minor > Fix For: 3.x > > > it would be nice to support trace breakpoints. > Most IDEs are providing this kind of feature. It allows to provide traces > during a debug session without modifying the source code. > see: > - > https://microsoft.github.io/debug-adapter-protocol/specification#Types_SourceBreakpoint > logMessage > - In IntelliJ, using non-suspended in combination with logging options > https://www.jetbrains.com/help/idea/using-breakpoints.html#suspend_policy > - In Eclipse, Tracepoint > https://www.eclipse.org/community/eclipse_newsletter/2017/june/article1.php > - In VS Code, Logpoint > https://code.visualstudio.com/docs/editor/debugging#_logpoints -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18105) camel-yaml-dsl - Trim property values for beans
[
https://issues.apache.org/jira/browse/CAMEL-18105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-18105.
-
Resolution: Won't Fix
> camel-yaml-dsl - Trim property values for beans
> ---
>
> Key: CAMEL-18105
> URL: https://issues.apache.org/jira/browse/CAMEL-18105
> Project: Camel
> Issue Type: Improvement
> Components: camel-yaml-dsl
>Reporter: Claus Ibsen
>Priority: Minor
> Fix For: 3.x
>
>
> You may mistakenly have spaces in a #bean reference in yaml-dsl where the
> value must be entered as string literal, with single or double quotes
> {code}
> - key: prefetchPolicy
> value: '#bean:{{sourcePrefetchPolicyBean}} '
> {code}
> There are spaces after the }} in the example above
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18097) camel-aws - Unable to override uri-endpoint-override override-endpoint options for STS
[
https://issues.apache.org/jira/browse/CAMEL-18097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18097:
Fix Version/s: 3.x
(was: 3.19.0)
> camel-aws - Unable to override uri-endpoint-override override-endpoint
> options for STS
> --
>
> Key: CAMEL-18097
> URL: https://issues.apache.org/jira/browse/CAMEL-18097
> Project: Camel
> Issue Type: Bug
> Components: camel-aws, camel-spring-boot
>Affects Versions: 3.14.2
>Reporter: Oreste Creolese
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 3.x
>
>
> Our goal is to no longer access AWS endpoints via a custom proxy but to
> access them via VPC endpoints from AWS. To make this work in our secured
> network we use our own VPC endpoints which we configure with the option:
> uri-endpoint-override (string) and override-endpoint (boolean). Now the
> problem is that the options are not used at all and the application always
> uses the default endpoints which have no access in our network. Because of
> this the STS component can't execute a HTTP request.
> *And in the console the following error message appears:*
> {code:java}
>
> Unable to execute HTTP request: Connect to sts.eu-central-1.amazonaws.com:443
> [sts.eu-central-1.amazonaws.com/54.239.54.207] failed: Connect timed out,
> ContainerCredentialsProvider(): Cannot fetch credentials from container -
> neither AWS_CONTAINER_CREDENTIALS_FULL_URI or
> AWS_CONTAINER_CREDENTIALS_RELATIVE_URI environment variables are set
> {code}
> As taken from the error message, the default endpoint
> sts.eu-central-1.amazonaws.com:443 is used.
> *This is how our application.properties looks in which the options are set:*
> {code:java}
> camel.component.aws2-sts.override-endpoint=true
> camel.component.aws2-sts.uri-endpoint-override=https://vpce-???-???.sts.eu
> central1.vpce.amazonaws.com{code}
> *We are using the following versions:*
> * Apache Camel 3.14.2
> * Spring Boot 2.5.10
> *Dependencies*
> {code:java}
>
> 14
> 3.14.2
> 2.5.10
>
>
>
> org.springframework.boot
> spring-boot-starter-test
> test
>
>
> org.springframework.boot
> spring-boot-starter-logging
>
>
>
>
>
> org.apache.camel.springboot
> camel-aws2-s3-starter
>
>
> org.springframework.boot
> spring-boot-starter-logging
>
>
>
>
>
> org.apache.camel.springboot
> camel-aws2-sts-starter
>
>
> org.springframework.boot
> spring-boot-starter-logging
>
>
>
>
> org.apache.camel
> camel-jetty
> ${camel.version}
>
>
> org.apache.camel
> camel-json-validator
> ${camel.version}
>
> {code}
> *Info* With ticket CAMEL-16171 , Camel added the usage of
> uri-endpoint-override and override-endpoint options attributes for all AWS
> components among others for STS.
> Do you have any idea why the options are not overwritten? Thanks a lot for
> your help!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18108) Add a id_str field to Twitter payload
[
https://issues.apache.org/jira/browse/CAMEL-18108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18108:
Priority: Minor (was: Major)
> Add a id_str field to Twitter payload
> -
>
> Key: CAMEL-18108
> URL: https://issues.apache.org/jira/browse/CAMEL-18108
> Project: Camel
> Issue Type: New Feature
> Components: camel-twitter
>Affects Versions: 3.16.0
>Reporter: Roland Huss
>Priority: Minor
>
> Since Twitter IDs as unsigned 64-bit integer values that [cannot be handled
> fully by
> JavaScript|https://github.com/Twitter4J/Twitter4J/pull/276#issuecomment-1125688911],
> the exposed {{id}} field as an integer can not be sealed with JavaScript.
> [Twitter has a {{id_str}} field in its REST
> API|https://developer.twitter.com/en/docs/twitter-ids], however, Twitter4J
> does not add this field to its response.
> Also, since [Twitter4J|https://github.com/Twitter4J/Twitter4J/pull/276] seems
> to refuse to add this field, it would be great if Camel could re-add it to
> its Twitter-related components.
> For a quick fix, I also created
> [https://github.com/apache/camel-kamelets/issues/925] so that this issue
> could be circumvented on the Camel-K level for Kamelet users.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18096) camel-kafka - Introduce TX options for kafka transaction
[ https://issues.apache.org/jira/browse/CAMEL-18096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18096: Fix Version/s: 3.x (was: 3.19.0) > camel-kafka - Introduce TX options for kafka transaction > > > Key: CAMEL-18096 > URL: https://issues.apache.org/jira/browse/CAMEL-18096 > Project: Camel > Issue Type: Improvement > Components: camel-kafka >Reporter: Zheng Feng >Assignee: Zheng Feng >Priority: Major > Fix For: 3.x > > > Currently it needs to use *addtional-properties* to enable kafka transaction. > It would be good if we could make configuring the TX options as new endpoint > options so its easier and more tooling friendly. Additional properties is > only intended for special and rare use-cases. > > * transactionalId -> addtional-properties[transactional.id] > * idempotence -> additional-properties[enable.idempotence] > * retries -> additional-properties[retries] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18108) Add a id_str field to Twitter payload
[
https://issues.apache.org/jira/browse/CAMEL-18108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18108:
Fix Version/s: 3.x
> Add a id_str field to Twitter payload
> -
>
> Key: CAMEL-18108
> URL: https://issues.apache.org/jira/browse/CAMEL-18108
> Project: Camel
> Issue Type: New Feature
> Components: camel-twitter
>Affects Versions: 3.16.0
>Reporter: Roland Huss
>Priority: Minor
> Fix For: 3.x
>
>
> Since Twitter IDs as unsigned 64-bit integer values that [cannot be handled
> fully by
> JavaScript|https://github.com/Twitter4J/Twitter4J/pull/276#issuecomment-1125688911],
> the exposed {{id}} field as an integer can not be sealed with JavaScript.
> [Twitter has a {{id_str}} field in its REST
> API|https://developer.twitter.com/en/docs/twitter-ids], however, Twitter4J
> does not add this field to its response.
> Also, since [Twitter4J|https://github.com/Twitter4J/Twitter4J/pull/276] seems
> to refuse to add this field, it would be great if Camel could re-add it to
> its Twitter-related components.
> For a quick fix, I also created
> [https://github.com/apache/camel-kamelets/issues/925] so that this issue
> could be circumvented on the Camel-K level for Kamelet users.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18090) camel-main - Loading properties with profiles for prod/dev/qa
[ https://issues.apache.org/jira/browse/CAMEL-18090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18090: Priority: Minor (was: Major) > camel-main - Loading properties with profiles for prod/dev/qa > - > > Key: CAMEL-18090 > URL: https://issues.apache.org/jira/browse/CAMEL-18090 > Project: Camel > Issue Type: New Feature > Components: camel-main >Reporter: Claus Ibsen >Priority: Minor > Fix For: 3.x > > > We may want to be able to have properties files that have property key=values > that are specific to profiles, so you can have %dev %prod %qa etc > Quarkus has something similar. > And spring boot have some kind of profile mechanism too. > However from tooling point of view its a bit more difficult as then a > properties file is not just plain key/value pairs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18081) camel-jbang - CLI property value from clipboard
[ https://issues.apache.org/jira/browse/CAMEL-18081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18081: Fix Version/s: 3.x > camel-jbang - CLI property value from clipboard > --- > > Key: CAMEL-18081 > URL: https://issues.apache.org/jira/browse/CAMEL-18081 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Priority: Minor > Fix For: 3.x > > > So you can quickly run something and provide a key=value where the value is > taken from clipboard, such as an api token etc. > However this if limited to a single clipboard value, so when you have many > its better to provide them as CLI args or properties files etc. > camel run foo.yaml --prop=secret-token=@clipboard@ > What kind of syntax to use? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18078) CamelGoogleSheets.valueInputOption not documented for google-sheets://data/append
[
https://issues.apache.org/jira/browse/CAMEL-18078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18078:
Component/s: documentation
> CamelGoogleSheets.valueInputOption not documented for
> google-sheets://data/append
> -
>
> Key: CAMEL-18078
> URL: https://issues.apache.org/jira/browse/CAMEL-18078
> Project: Camel
> Issue Type: Improvement
> Components: documentation, google-sheets
>Reporter: Peter Palaga
>Priority: Minor
> Fix For: 3.x
>
>
> Having a route like the following
> {code}
> from("timer:tick?period=3s").setBody().constant("foobar")
> .log("${body}")
> .process(exchange -> {
> final Message m = exchange.getMessage();
> //m.setHeader("CamelGoogleSheets.valueInputOption",
> "RAW");
> m.setHeader("CamelGoogleSheets.values",
> new ValueRange().setValues(
> Arrays.asList(
> Arrays.asList(
>
> m.getBody(String.class);
> })
>
> .to("google-sheets://data/append?spreadsheetId={{google-sheets.spreadsheet-id}}=Sheet1!A1:A1");
> {code}
> results in the following exception unless one uncomments
> {{m.setHeader("CamelGoogleSheets.valueInputOption", "RAW")}}:
> {code}
> org.apache.camel.RuntimeCamelException:
> com.google.api.client.googleapis.json.GoogleJsonResponseException: 400 Bad
> Request
> POST
> https://sheets.googleapis.com/v4/spreadsheets/12dtOvsosJ4l1vIfLRqD8bZXyzLk0iGI4ENzN6qi_ys8/values/Sheet1!A1:A1:append
> {
> "code" : 400,
> "errors" : [ {
> "domain" : "global",
> "message" : "'valueInputOption' is required but not specified",
> "reason" : "badRequest"
> } ],
> "message" : "'valueInputOption' is required but not specified",
> "status" : "INVALID_ARGUMENT"
> }
> at
> org.apache.camel.component.google.sheets.GoogleSheetsProducer.doInvokeMethod(GoogleSheetsProducer.java:51)
> at
> org.apache.camel.support.component.AbstractApiProducer$1.run(AbstractApiProducer.java:89)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Caused by: com.google.api.client.googleapis.json.GoogleJsonResponseException:
> 400 Bad Request
> POST
> https://sheets.googleapis.com/v4/spreadsheets/12dtOvsosJ4l1vIfLRqD8bZXyzLk0iGI4ENzN6qi_ys8/values/Sheet1!A1:A1:append
> {
> "code" : 400,
> "errors" : [ {
> "domain" : "global",
> "message" : "'valueInputOption' is required but not specified",
> "reason" : "badRequest"
> } ],
> "message" : "'valueInputOption' is required but not specified",
> "status" : "INVALID_ARGUMENT"
> }
> at
> com.google.api.client.googleapis.json.GoogleJsonResponseException.from(GoogleJsonResponseException.java:146)
> at
> com.google.api.client.googleapis.services.json.AbstractGoogleJsonClientRequest.newExceptionOnError(AbstractGoogleJsonClientRequest.java:118)
> at
> com.google.api.client.googleapis.services.json.AbstractGoogleJsonClientRequest.newExceptionOnError(AbstractGoogleJsonClientRequest.java:37)
> at
> com.google.api.client.googleapis.services.AbstractGoogleClientRequest$1.interceptResponse(AbstractGoogleClientRequest.java:428)
> at
> com.google.api.client.http.HttpRequest.execute(HttpRequest.java:)
> at
> com.google.api.client.googleapis.services.AbstractGoogleClientRequest.executeUnparsed(AbstractGoogleClientRequest.java:514)
> at
> com.google.api.client.googleapis.services.AbstractGoogleClientRequest.executeUnparsed(AbstractGoogleClientRequest.java:455)
> at
> com.google.api.client.googleapis.services.AbstractGoogleClientRequest.execute(AbstractGoogleClientRequest.java:565)
> at
> org.apache.camel.component.google.sheets.GoogleSheetsProducer.doInvokeMethod(GoogleSheetsProducer.java:49)
> ... 7 more
> {code}
> It would be nice to document the header around here:
> https://camel.apache.org/components/latest/google-sheets-component.html#_api_data_method_append
> Possible values are {{RAW}} and {{USER_ENTERED}}.
> Also, I wonder whether the
[jira] [Updated] (CAMEL-18078) CamelGoogleSheets.valueInputOption not documented for google-sheets://data/append
[
https://issues.apache.org/jira/browse/CAMEL-18078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18078:
Fix Version/s: 3.x
> CamelGoogleSheets.valueInputOption not documented for
> google-sheets://data/append
> -
>
> Key: CAMEL-18078
> URL: https://issues.apache.org/jira/browse/CAMEL-18078
> Project: Camel
> Issue Type: Improvement
> Components: google-sheets
>Reporter: Peter Palaga
>Priority: Minor
> Fix For: 3.x
>
>
> Having a route like the following
> {code}
> from("timer:tick?period=3s").setBody().constant("foobar")
> .log("${body}")
> .process(exchange -> {
> final Message m = exchange.getMessage();
> //m.setHeader("CamelGoogleSheets.valueInputOption",
> "RAW");
> m.setHeader("CamelGoogleSheets.values",
> new ValueRange().setValues(
> Arrays.asList(
> Arrays.asList(
>
> m.getBody(String.class);
> })
>
> .to("google-sheets://data/append?spreadsheetId={{google-sheets.spreadsheet-id}}=Sheet1!A1:A1");
> {code}
> results in the following exception unless one uncomments
> {{m.setHeader("CamelGoogleSheets.valueInputOption", "RAW")}}:
> {code}
> org.apache.camel.RuntimeCamelException:
> com.google.api.client.googleapis.json.GoogleJsonResponseException: 400 Bad
> Request
> POST
> https://sheets.googleapis.com/v4/spreadsheets/12dtOvsosJ4l1vIfLRqD8bZXyzLk0iGI4ENzN6qi_ys8/values/Sheet1!A1:A1:append
> {
> "code" : 400,
> "errors" : [ {
> "domain" : "global",
> "message" : "'valueInputOption' is required but not specified",
> "reason" : "badRequest"
> } ],
> "message" : "'valueInputOption' is required but not specified",
> "status" : "INVALID_ARGUMENT"
> }
> at
> org.apache.camel.component.google.sheets.GoogleSheetsProducer.doInvokeMethod(GoogleSheetsProducer.java:51)
> at
> org.apache.camel.support.component.AbstractApiProducer$1.run(AbstractApiProducer.java:89)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Caused by: com.google.api.client.googleapis.json.GoogleJsonResponseException:
> 400 Bad Request
> POST
> https://sheets.googleapis.com/v4/spreadsheets/12dtOvsosJ4l1vIfLRqD8bZXyzLk0iGI4ENzN6qi_ys8/values/Sheet1!A1:A1:append
> {
> "code" : 400,
> "errors" : [ {
> "domain" : "global",
> "message" : "'valueInputOption' is required but not specified",
> "reason" : "badRequest"
> } ],
> "message" : "'valueInputOption' is required but not specified",
> "status" : "INVALID_ARGUMENT"
> }
> at
> com.google.api.client.googleapis.json.GoogleJsonResponseException.from(GoogleJsonResponseException.java:146)
> at
> com.google.api.client.googleapis.services.json.AbstractGoogleJsonClientRequest.newExceptionOnError(AbstractGoogleJsonClientRequest.java:118)
> at
> com.google.api.client.googleapis.services.json.AbstractGoogleJsonClientRequest.newExceptionOnError(AbstractGoogleJsonClientRequest.java:37)
> at
> com.google.api.client.googleapis.services.AbstractGoogleClientRequest$1.interceptResponse(AbstractGoogleClientRequest.java:428)
> at
> com.google.api.client.http.HttpRequest.execute(HttpRequest.java:)
> at
> com.google.api.client.googleapis.services.AbstractGoogleClientRequest.executeUnparsed(AbstractGoogleClientRequest.java:514)
> at
> com.google.api.client.googleapis.services.AbstractGoogleClientRequest.executeUnparsed(AbstractGoogleClientRequest.java:455)
> at
> com.google.api.client.googleapis.services.AbstractGoogleClientRequest.execute(AbstractGoogleClientRequest.java:565)
> at
> org.apache.camel.component.google.sheets.GoogleSheetsProducer.doInvokeMethod(GoogleSheetsProducer.java:49)
> ... 7 more
> {code}
> It would be nice to document the header around here:
> https://camel.apache.org/components/latest/google-sheets-component.html#_api_data_method_append
> Possible values are {{RAW}} and {{USER_ENTERED}}.
> Also, I wonder whether the {{valueInputOption}} could
[jira] [Updated] (CAMEL-18082) camel-jbang - Prompt mode for required values
[ https://issues.apache.org/jira/browse/CAMEL-18082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18082: Fix Version/s: 3.x > camel-jbang - Prompt mode for required values > - > > Key: CAMEL-18082 > URL: https://issues.apache.org/jira/browse/CAMEL-18082 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.x > > > So you can run something where a set of required values have not been > provided, such as username / passwords etc. > camel run foo.xml > And then camel-jbang will prompt for missing values > Enter value for s3-api-token: XXX > Enter value for s3-secret-token: XXX > ... > Then you can copy/paste those in the prompt. -- This message was sent by Atlassian Jira (v8.20.10#820010)
