[jira] [Resolved] (CAMEL-18968) Camel-aws2-sqs - Queue url might stay empty for the delayed queue.
[ https://issues.apache.org/jira/browse/CAMEL-18968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18968. -- Resolution: Fixed > Camel-aws2-sqs - Queue url might stay empty for the delayed queue. > -- > > Key: CAMEL-18968 > URL: https://issues.apache.org/jira/browse/CAMEL-18968 > Project: Camel > Issue Type: Bug > Components: camel-aws2 >Affects Versions: 3.20.1 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 3.18.5, 3.20.2, 3.21.0, 4.0 > > > During investigation of [https://github.com/apache/camel-quarkus/issues/4389] > I found that aws2-sqs producer is not able to send messages to the queueu > which was created as delayed. > > Queue url should be initialized during the endpoint initialization phase. If > queue does not exist in that time, the url stays empty for the whole life of > the endpoint. Therefore majority of actions would fail. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18976) camel file storage copyObject support for multiple authenticated client
[ https://issues.apache.org/jira/browse/CAMEL-18976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17680285#comment-17680285 ] Andrea Cosentino commented on CAMEL-18976: -- I don't think it makes sense a second client or a second set of credentials in parameters or headers or wherever. This will only pollute the endpoint options. You have the ability to do the operation through two different operations. I don't think it worths to introduce more complexities just for one single operation corner case. > camel file storage copyObject support for multiple authenticated client > --- > > Key: CAMEL-18976 > URL: https://issues.apache.org/jira/browse/CAMEL-18976 > Project: Camel > Issue Type: New Feature > Components: camel-aws2, camel-azure, camel-google-storage, > camel-minio >Affects Versions: 3.20.1, 4.0, Future >Reporter: Hitesh C >Priority: Major > > Presently Copy Object operation works well when the same set of credentials > have access to both source and destination buckets. > So when i am performing copy object from an S3 bucket to another S3 bucket > with different set of credentials, I have to do a getObject and PutObject > operation separately. > > An functionality accepting a pair of client (s3, minio, cloud-storage), etc > and the respective storage bucket as source and destination could help in > simplifying the process even further. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18971) Camel-Spring-Boot: Add SBOM generation
Andrea Cosentino created CAMEL-18971: Summary: Camel-Spring-Boot: Add SBOM generation Key: CAMEL-18971 URL: https://issues.apache.org/jira/browse/CAMEL-18971 Project: Camel Issue Type: Task Components: camel-spring-boot Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.0 Like we have in Camel. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18970) Camel-Any23: Remove component
Andrea Cosentino created CAMEL-18970: Summary: Camel-Any23: Remove component Key: CAMEL-18970 URL: https://issues.apache.org/jira/browse/CAMEL-18970 Project: Camel Issue Type: Task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.0 This component is on 2.7 from too much time and there doesn't seem to be a release on the horizon. It's full of out-of-date dependencies and not really maintained even on our side, so I think it's better removing it on 4.x and deprecate on 3.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18968) Camel-aws2-sqs - Queue url might stay empty for the delayed queue.
[ https://issues.apache.org/jira/browse/CAMEL-18968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-18968: - Fix Version/s: 3.18.5 > Camel-aws2-sqs - Queue url might stay empty for the delayed queue. > -- > > Key: CAMEL-18968 > URL: https://issues.apache.org/jira/browse/CAMEL-18968 > Project: Camel > Issue Type: Bug > Components: camel-aws2 >Affects Versions: 3.20.1 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 3.18.5, 3.20.2, 3.21.0, 4.0 > > > During investigation of [https://github.com/apache/camel-quarkus/issues/4389] > I found that aws2-sqs producer is not able to send messages to the queueu > which was created as delayed. > > Queue url should be initialized during the endpoint initialization phase. If > queue does not exist in that time, the url stays empty for the whole life of > the endpoint. Therefore majority of actions would fail. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18968) Camel-aws2-sqs - Queue url might stay empty for the delayed queue.
[ https://issues.apache.org/jira/browse/CAMEL-18968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-18968: - Fix Version/s: 3.20.2 3.21.0 4.0 > Camel-aws2-sqs - Queue url might stay empty for the delayed queue. > -- > > Key: CAMEL-18968 > URL: https://issues.apache.org/jira/browse/CAMEL-18968 > Project: Camel > Issue Type: Bug > Components: camel-aws2 >Affects Versions: 3.20.1 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 3.20.2, 3.21.0, 4.0 > > > During investigation of [https://github.com/apache/camel-quarkus/issues/4389] > I found that aws2-sqs producer is not able to send messages to the queueu > which was created as delayed. > > Queue url should be initialized during the endpoint initialization phase. If > queue does not exist in that time, the url stays empty for the whole life of > the endpoint. Therefore majority of actions would fail. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18965) Camel-CXF: OnCompletion not working anymore
[
https://issues.apache.org/jira/browse/CAMEL-18965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-18965:
-
Summary: Camel-CXF: OnCompletion not working anymore (was: OnCompletion
not working anymore)
> Camel-CXF: OnCompletion not working anymore
> ---
>
> Key: CAMEL-18965
> URL: https://issues.apache.org/jira/browse/CAMEL-18965
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
>Affects Versions: 3.11.1
>Reporter: Manuel Shenavai
>Priority: Major
>
> Since following change, the onCompletionHandler is not called anymore in
> error case (soap fault)
> https://issues.apache.org/jira/browse/CAMEL-16796
> [https://github.com/apache/camel/commit/45e64cce8ad2e1d22a5f55be13a6dfcaa504f58f]
> {*}Reproducer{*}: [https://github.com/mash-sap/CAMEL-16532/tree/Camel-18965]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18965) OnCompletion not working anymore
[
https://issues.apache.org/jira/browse/CAMEL-18965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17679752#comment-17679752
]
Andrea Cosentino commented on CAMEL-18965:
--
Did you try with 3.18.x and 3.20.x?
> OnCompletion not working anymore
>
>
> Key: CAMEL-18965
> URL: https://issues.apache.org/jira/browse/CAMEL-18965
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
>Affects Versions: 3.11.1
>Reporter: Manuel Shenavai
>Priority: Major
>
> Since following change, the onCompletionHandler is not called anymore in
> error case (soap fault)
> https://issues.apache.org/jira/browse/CAMEL-16796
> [https://github.com/apache/camel/commit/45e64cce8ad2e1d22a5f55be13a6dfcaa504f58f]
> {*}Reproducer{*}: [https://github.com/mash-sap/CAMEL-16532/tree/Camel-18965]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18956) Camel-Jcache: It's using a bundle of javax-cache-api
[ https://issues.apache.org/jira/browse/CAMEL-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18956. -- Resolution: Fixed > Camel-Jcache: It's using a bundle of javax-cache-api > > > Key: CAMEL-18956 > URL: https://issues.apache.org/jira/browse/CAMEL-18956 > Project: Camel > Issue Type: Bug >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.0 > > > It's not part of Jakarta move, but I guess we should use the normal > dependency and not the bundle. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18907) camel-datasonnet - Datasonnet is not JakartaEE compatible for v4
[ https://issues.apache.org/jira/browse/CAMEL-18907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17679725#comment-17679725 ] Andrea Cosentino commented on CAMEL-18907: -- You should revert the commit removing the component and start to align from there I think. > camel-datasonnet - Datasonnet is not JakartaEE compatible for v4 > > > Key: CAMEL-18907 > URL: https://issues.apache.org/jira/browse/CAMEL-18907 > Project: Camel > Issue Type: Task >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.0 > > > Reported this to datasonnet at > https://github.com/datasonnet/datasonnet-mapper/issues/112 > Until there is a Jakarta compatible release, then we would need to > disable/remove camel-datasonnet. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18907) camel-datasonnet - Datasonnet is not JakartaEE compatible for v4
[ https://issues.apache.org/jira/browse/CAMEL-18907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17678823#comment-17678823 ] Andrea Cosentino commented on CAMEL-18907: -- The component has been removed from the codebase, I think we first need to upgrade to 2.5 and then try the Jakarta one, if everything works we could add it back. > camel-datasonnet - Datasonnet is not JakartaEE compatible for v4 > > > Key: CAMEL-18907 > URL: https://issues.apache.org/jira/browse/CAMEL-18907 > Project: Camel > Issue Type: Task >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.0 > > > Reported this to datasonnet at > https://github.com/datasonnet/datasonnet-mapper/issues/112 > Until there is a Jakarta compatible release, then we would need to > disable/remove camel-datasonnet. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18956) Camel-Jcache: It's using a bundle of javax-cache-api
Andrea Cosentino created CAMEL-18956: Summary: Camel-Jcache: It's using a bundle of javax-cache-api Key: CAMEL-18956 URL: https://issues.apache.org/jira/browse/CAMEL-18956 Project: Camel Issue Type: Bug Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.0 It's not part of Jakarta move, but I guess we should use the normal dependency and not the bundle. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18951) Introducing SBOM generation
Andrea Cosentino created CAMEL-18951: Summary: Introducing SBOM generation Key: CAMEL-18951 URL: https://issues.apache.org/jira/browse/CAMEL-18951 Project: Camel Issue Type: Improvement Components: build system Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.0 We could use some of the maven plugin out there: https://github.com/CycloneDX/cyclonedx-maven-plugin To me this one is really complete. For the beginning I will use a profile without adding the generated SBOM to the assembly (I don't know how big will it be), but I do believe it would be really helpful and I would like to add it as standard information with each release -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18949) camel-examples - Remove examples using removed components
[ https://issues.apache.org/jira/browse/CAMEL-18949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18949. -- Resolution: Fixed > camel-examples - Remove examples using removed components > - > > Key: CAMEL-18949 > URL: https://issues.apache.org/jira/browse/CAMEL-18949 > Project: Camel > Issue Type: Task > Components: examples >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.0 > > > camel-examples > camel-spring-boot-examples -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18949) camel-examples - Remove examples using removed components
[ https://issues.apache.org/jira/browse/CAMEL-18949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17678235#comment-17678235 ] Andrea Cosentino commented on CAMEL-18949: -- Done for Spring-boot-examples > camel-examples - Remove examples using removed components > - > > Key: CAMEL-18949 > URL: https://issues.apache.org/jira/browse/CAMEL-18949 > Project: Camel > Issue Type: Task > Components: examples >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.0 > > > camel-examples > camel-spring-boot-examples -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18949) camel-examples - Remove examples using removed components
[ https://issues.apache.org/jira/browse/CAMEL-18949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17678218#comment-17678218 ] Andrea Cosentino commented on CAMEL-18949: -- Done for camel-examples. > camel-examples - Remove examples using removed components > - > > Key: CAMEL-18949 > URL: https://issues.apache.org/jira/browse/CAMEL-18949 > Project: Camel > Issue Type: Task > Components: examples >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.0 > > > camel-examples > camel-spring-boot-examples -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18949) camel-examples - Remove examples using removed components
[ https://issues.apache.org/jira/browse/CAMEL-18949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-18949: Assignee: Andrea Cosentino > camel-examples - Remove examples using removed components > - > > Key: CAMEL-18949 > URL: https://issues.apache.org/jira/browse/CAMEL-18949 > Project: Camel > Issue Type: Task > Components: examples >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.0 > > > camel-examples > camel-spring-boot-examples -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18939) camel-examples - Migrate to logger 2 in v2
[ https://issues.apache.org/jira/browse/CAMEL-18939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18939. -- Resolution: Fixed > camel-examples - Migrate to logger 2 in v2 > -- > > Key: CAMEL-18939 > URL: https://issues.apache.org/jira/browse/CAMEL-18939 > Project: Camel > Issue Type: Task > Components: examples >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.0 > > > The standalone examples likely need to have pom.xml updated to log4j2 upgrade > https://github.com/apache/camel-examples -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18936) components - Add log4j-core so logging to logfile works
[
https://issues.apache.org/jira/browse/CAMEL-18936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-18936.
--
Resolution: Fixed
> components - Add log4j-core so logging to logfile works
> ---
>
> Key: CAMEL-18936
> URL: https://issues.apache.org/jira/browse/CAMEL-18936
> Project: Camel
> Issue Type: Task
>Reporter: Claus Ibsen
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.0
>
>
> To make logging work we need to make sure we have these 2 test dependencies
> {code}
>
> org.apache.logging.log4j
> log4j-core
> test
>
>
> org.apache.logging.log4j
> log4j-slf4j2-impl
> test
>
> {code}
> Most often we only have
> {code}
>
> org.apache.logging.log4j
> log4j-slf4j2-impl
> test
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18939) camel-examples - Migrate to logger 2 in v2
[ https://issues.apache.org/jira/browse/CAMEL-18939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17677677#comment-17677677 ] Andrea Cosentino commented on CAMEL-18939: -- We first need to switch to 4.0.0-SNAPSHOT > camel-examples - Migrate to logger 2 in v2 > -- > > Key: CAMEL-18939 > URL: https://issues.apache.org/jira/browse/CAMEL-18939 > Project: Camel > Issue Type: Task > Components: examples >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.0 > > > The standalone examples likely need to have pom.xml updated to log4j2 upgrade > https://github.com/apache/camel-examples -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18939) camel-examples - Migrate to logger 2 in v2
[ https://issues.apache.org/jira/browse/CAMEL-18939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17677676#comment-17677676 ] Andrea Cosentino commented on CAMEL-18939: -- Assigning this to me for completing this week > camel-examples - Migrate to logger 2 in v2 > -- > > Key: CAMEL-18939 > URL: https://issues.apache.org/jira/browse/CAMEL-18939 > Project: Camel > Issue Type: Task > Components: examples >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.0 > > > The standalone examples likely need to have pom.xml updated to log4j2 upgrade > https://github.com/apache/camel-examples -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18939) camel-examples - Migrate to logger 2 in v2
[ https://issues.apache.org/jira/browse/CAMEL-18939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-18939: Assignee: Andrea Cosentino > camel-examples - Migrate to logger 2 in v2 > -- > > Key: CAMEL-18939 > URL: https://issues.apache.org/jira/browse/CAMEL-18939 > Project: Camel > Issue Type: Task > Components: examples >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.0 > > > The standalone examples likely need to have pom.xml updated to log4j2 upgrade > https://github.com/apache/camel-examples -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18936) components - Add log4j-core so logging to logfile works
[
https://issues.apache.org/jira/browse/CAMEL-18936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17677643#comment-17677643
]
Andrea Cosentino commented on CAMEL-18936:
--
Done. I need to align the archetypes to complete it all.
> components - Add log4j-core so logging to logfile works
> ---
>
> Key: CAMEL-18936
> URL: https://issues.apache.org/jira/browse/CAMEL-18936
> Project: Camel
> Issue Type: Task
>Reporter: Claus Ibsen
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.0
>
>
> To make logging work we need to make sure we have these 2 test dependencies
> {code}
>
> org.apache.logging.log4j
> log4j-core
> test
>
>
> org.apache.logging.log4j
> log4j-slf4j2-impl
> test
>
> {code}
> Most often we only have
> {code}
>
> org.apache.logging.log4j
> log4j-slf4j2-impl
> test
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18936) components - Add log4j-core so logging to logfile works
[
https://issues.apache.org/jira/browse/CAMEL-18936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17677473#comment-17677473
]
Andrea Cosentino commented on CAMEL-18936:
--
I'll try to go with #1, for the beginning I'll remove the log4j and slfj, after
that we could revisit for hamcrest and the others.
> components - Add log4j-core so logging to logfile works
> ---
>
> Key: CAMEL-18936
> URL: https://issues.apache.org/jira/browse/CAMEL-18936
> Project: Camel
> Issue Type: Task
>Reporter: Claus Ibsen
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.0
>
>
> To make logging work we need to make sure we have these 2 test dependencies
> {code}
>
> org.apache.logging.log4j
> log4j-core
> test
>
>
> org.apache.logging.log4j
> log4j-slf4j2-impl
> test
>
> {code}
> Most often we only have
> {code}
>
> org.apache.logging.log4j
> log4j-slf4j2-impl
> test
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-18936) components - Add log4j-core so logging to logfile works
[
https://issues.apache.org/jira/browse/CAMEL-18936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino reassigned CAMEL-18936:
Assignee: Andrea Cosentino
> components - Add log4j-core so logging to logfile works
> ---
>
> Key: CAMEL-18936
> URL: https://issues.apache.org/jira/browse/CAMEL-18936
> Project: Camel
> Issue Type: Task
>Reporter: Claus Ibsen
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.0
>
>
> To make logging work we need to make sure we have these 2 test dependencies
> {code}
>
> org.apache.logging.log4j
> log4j-core
> test
>
>
> org.apache.logging.log4j
> log4j-slf4j2-impl
> test
>
> {code}
> Most often we only have
> {code}
>
> org.apache.logging.log4j
> log4j-slf4j2-impl
> test
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18936) components - Add log4j-core so logging to logfile works
[
https://issues.apache.org/jira/browse/CAMEL-18936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17677452#comment-17677452
]
Andrea Cosentino commented on CAMEL-18936:
--
I'm on it already. I'll try to complete all the needed part between today and
tomorrow.
> components - Add log4j-core so logging to logfile works
> ---
>
> Key: CAMEL-18936
> URL: https://issues.apache.org/jira/browse/CAMEL-18936
> Project: Camel
> Issue Type: Task
>Reporter: Claus Ibsen
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.0
>
>
> To make logging work we need to make sure we have these 2 test dependencies
> {code}
>
> org.apache.logging.log4j
> log4j-core
> test
>
>
> org.apache.logging.log4j
> log4j-slf4j2-impl
> test
>
> {code}
> Most often we only have
> {code}
>
> org.apache.logging.log4j
> log4j-slf4j2-impl
> test
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-18929) camel-spring-boot - Remove deprecated components in v4
[ https://issues.apache.org/jira/browse/CAMEL-18929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-18929: Assignee: Andrea Cosentino > camel-spring-boot - Remove deprecated components in v4 > -- > > Key: CAMEL-18929 > URL: https://issues.apache.org/jira/browse/CAMEL-18929 > Project: Camel > Issue Type: Task > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.0 > > > The following components has been removed: > - camel-atmos > - camel-caffeine-lrucache > - camel-cdi > - camel-elasticsearch-rest > - camel-gora > - camel-hbase > - camel-iota > - camel-ipfs > - camel-jclouds > - camel-microprofile-metrics > - camel-opentracing > - camel-rabbitmq > - camel-rest-swagger > - camel-restdsl-swagger-plugin > - camel-resteasy > - camel-spark > - camel-swagger-java > - camel-websocket-jsr356 > - camel-xstream > - camel-zikin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18929) camel-spring-boot - Remove deprecated components in v4
[ https://issues.apache.org/jira/browse/CAMEL-18929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17677246#comment-17677246 ] Andrea Cosentino commented on CAMEL-18929: -- I'll do A-M for the beginning > camel-spring-boot - Remove deprecated components in v4 > -- > > Key: CAMEL-18929 > URL: https://issues.apache.org/jira/browse/CAMEL-18929 > Project: Camel > Issue Type: Task > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.0 > > > The following components has been removed: > - camel-atmos > - camel-caffeine-lrucache > - camel-cdi > - camel-elasticsearch-rest > - camel-gora > - camel-hbase > - camel-iota > - camel-ipfs > - camel-jclouds > - camel-microprofile-metrics > - camel-opentracing > - camel-rabbitmq > - camel-rest-swagger > - camel-restdsl-swagger-plugin > - camel-resteasy > - camel-spark > - camel-swagger-java > - camel-websocket-jsr356 > - camel-xstream > - camel-zikin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18912) Sqs2ConsumerHealthCheck is broken when using injected client
[ https://issues.apache.org/jira/browse/CAMEL-18912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17676561#comment-17676561 ] Andrea Cosentino commented on CAMEL-18912: -- I think this would be a problem in all the components related to AWS. We thought about client from configuration, client built from parameters and if not we create the client with default credentials provider. Silly me, didn't think about the autowired ones. Sorry. > Sqs2ConsumerHealthCheck is broken when using injected client > > > Key: CAMEL-18912 > URL: https://issues.apache.org/jira/browse/CAMEL-18912 > Project: Camel > Issue Type: Improvement > Components: camel-aws2 >Affects Versions: 3.19.0, 3.20.0, 3.20.1 >Reporter: Simon Rasmussen >Priority: Major > Fix For: 3.20.2, 3.21.0, 4.0 > > > Cased by CAMEL-18466 where a new health check is introduced for the SQS > component. > The component creates it own client, but does so incorrectly as it fails to > detect if a client is injected. > Also, the client is created for every invocation of the health check which is > not very efficient, a better solution would be to pass in the SqsClient to > the health check itself. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18912) Sqs2ConsumerHealthCheck is broken when using injected client
[ https://issues.apache.org/jira/browse/CAMEL-18912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17676554#comment-17676554 ] Andrea Cosentino edited comment on CAMEL-18912 at 1/13/23 10:16 AM: So you're using a client from the registry and it is autowired? was (Author: ancosen): So you're using a client from the registry? > Sqs2ConsumerHealthCheck is broken when using injected client > > > Key: CAMEL-18912 > URL: https://issues.apache.org/jira/browse/CAMEL-18912 > Project: Camel > Issue Type: Bug > Components: camel-aws2 >Affects Versions: 3.19.0, 3.20.0, 3.20.1 >Reporter: Simon Rasmussen >Priority: Major > > Cased by CAMEL-18466 where a new health check is introduced for the SQS > component. > The component creates it own client, but does so incorrectly as it fails to > detect if a client is injected. > Also, the client is created for every invocation of the health check which is > not very efficient, a better solution would be to pass in the SqsClient to > the health check itself. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18912) Sqs2ConsumerHealthCheck is broken when using injected client
[ https://issues.apache.org/jira/browse/CAMEL-18912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17676554#comment-17676554 ] Andrea Cosentino commented on CAMEL-18912: -- So you're using a client from the registry? > Sqs2ConsumerHealthCheck is broken when using injected client > > > Key: CAMEL-18912 > URL: https://issues.apache.org/jira/browse/CAMEL-18912 > Project: Camel > Issue Type: Bug > Components: camel-aws2 >Affects Versions: 3.19.0, 3.20.0, 3.20.1 >Reporter: Simon Rasmussen >Priority: Major > > Cased by CAMEL-18466 where a new health check is introduced for the SQS > component. > The component creates it own client, but does so incorrectly as it fails to > detect if a client is injected. > Also, the client is created for every invocation of the health check which is > not very efficient, a better solution would be to pass in the SqsClient to > the health check itself. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18890) Remove camel-vertx-kafka
[ https://issues.apache.org/jira/browse/CAMEL-18890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18890. -- Resolution: Fixed > Remove camel-vertx-kafka > > > Key: CAMEL-18890 > URL: https://issues.apache.org/jira/browse/CAMEL-18890 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18889) Remove camel-rabbitmq
[ https://issues.apache.org/jira/browse/CAMEL-18889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18889. -- Resolution: Fixed > Remove camel-rabbitmq > - > > Key: CAMEL-18889 > URL: https://issues.apache.org/jira/browse/CAMEL-18889 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18896) Remove camel-iota in v4
[ https://issues.apache.org/jira/browse/CAMEL-18896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-18896: Assignee: Andrea Cosentino > Remove camel-iota in v4 > --- > > Key: CAMEL-18896 > URL: https://issues.apache.org/jira/browse/CAMEL-18896 > Project: Camel > Issue Type: Sub-task >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18893) Camel-Examples: Switch to Camel 4.x
Andrea Cosentino created CAMEL-18893: Summary: Camel-Examples: Switch to Camel 4.x Key: CAMEL-18893 URL: https://issues.apache.org/jira/browse/CAMEL-18893 Project: Camel Issue Type: Task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.0 There are a bunch of example using stuff like camel-activemq, camel-websocket etc. We need to remove them and restart from scratch. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18890) Remove camel-vertx-kafka
Andrea Cosentino created CAMEL-18890: Summary: Remove camel-vertx-kafka Key: CAMEL-18890 URL: https://issues.apache.org/jira/browse/CAMEL-18890 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18885) camel-johnzon - Make this component work in v4 if possible
[ https://issues.apache.org/jira/browse/CAMEL-18885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17675915#comment-17675915 ] Andrea Cosentino commented on CAMEL-18885: -- They are moving: https://github.com/apache/johnzon/commits/master > camel-johnzon - Make this component work in v4 if possible > -- > > Key: CAMEL-18885 > URL: https://issues.apache.org/jira/browse/CAMEL-18885 > Project: Camel > Issue Type: Task > Components: camel-johnzon >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18889) Remove camel-rabbitmq
Andrea Cosentino created CAMEL-18889: Summary: Remove camel-rabbitmq Key: CAMEL-18889 URL: https://issues.apache.org/jira/browse/CAMEL-18889 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18879) Remove Camel-Zipkin after deprecation
[ https://issues.apache.org/jira/browse/CAMEL-18879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18879. -- Resolution: Fixed > Remove Camel-Zipkin after deprecation > - > > Key: CAMEL-18879 > URL: https://issues.apache.org/jira/browse/CAMEL-18879 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.0 > > > I think we should remove it for Camel 4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18877) camel-caffeine - Key should be string type
[ https://issues.apache.org/jira/browse/CAMEL-18877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18877. -- Resolution: Fixed > camel-caffeine - Key should be string type > -- > > Key: CAMEL-18877 > URL: https://issues.apache.org/jira/browse/CAMEL-18877 > Project: Camel > Issue Type: Improvement > Components: camel-caffeine >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.21.0, 4.0 > > > The key is Object type which is too generic, and its better to use a String > type. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18877) camel-caffeine - Key should be string type
[ https://issues.apache.org/jira/browse/CAMEL-18877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-18877: - Fix Version/s: 4.0 > camel-caffeine - Key should be string type > -- > > Key: CAMEL-18877 > URL: https://issues.apache.org/jira/browse/CAMEL-18877 > Project: Camel > Issue Type: Improvement > Components: camel-caffeine >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.21.0, 4.0 > > > The key is Object type which is too generic, and its better to use a String > type. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18877) camel-caffeine - Key should be string type
[ https://issues.apache.org/jira/browse/CAMEL-18877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17675573#comment-17675573 ] Andrea Cosentino commented on CAMEL-18877: -- This will require the removal of keyType parameter > camel-caffeine - Key should be string type > -- > > Key: CAMEL-18877 > URL: https://issues.apache.org/jira/browse/CAMEL-18877 > Project: Camel > Issue Type: Improvement > Components: camel-caffeine >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.21.0 > > > The key is Object type which is too generic, and its better to use a String > type. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18496) Remove deprecated components
[ https://issues.apache.org/jira/browse/CAMEL-18496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17671911#comment-17671911 ] Andrea Cosentino commented on CAMEL-18496: -- Since we are switching to Camel 4 I'm going to open an issue to remove also Camel Zipkin. > Remove deprecated components > > > Key: CAMEL-18496 > URL: https://issues.apache.org/jira/browse/CAMEL-18496 > Project: Camel > Issue Type: Task >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 3.21.0 > > > * camel-ahc: CAMEL-17667 > * camel-ahc-ws: CAMEL-17667 > * camel-dozer: CAMEL-18455 > * camel-cmis: https://issues.apache.org/jira/browse/CAMEL-18495 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18879) Remove Camel-Zipkin after deprecation
Andrea Cosentino created CAMEL-18879: Summary: Remove Camel-Zipkin after deprecation Key: CAMEL-18879 URL: https://issues.apache.org/jira/browse/CAMEL-18879 Project: Camel Issue Type: Task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.0 I think we should remove it for Camel 4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18877) camel-caffeine - Key should be string type
[ https://issues.apache.org/jira/browse/CAMEL-18877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-18877: Assignee: Andrea Cosentino > camel-caffeine - Key should be string type > -- > > Key: CAMEL-18877 > URL: https://issues.apache.org/jira/browse/CAMEL-18877 > Project: Camel > Issue Type: Improvement > Components: camel-caffeine >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.21.0 > > > The key is Object type which is too generic, and its better to use a String > type. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18873) Camel-Elasticsearch: CertificatePath should be readable through ResourceHelper
[ https://issues.apache.org/jira/browse/CAMEL-18873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18873. -- Resolution: Fixed > Camel-Elasticsearch: CertificatePath should be readable through ResourceHelper > -- > > Key: CAMEL-18873 > URL: https://issues.apache.org/jira/browse/CAMEL-18873 > Project: Camel > Issue Type: Improvement > Components: camel-elasticsearch >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.21.0, 4.0 > > > Instead of specifying a fixed path, we could in this way read from classpath, > http etc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18873) Camel-Elasticsearch: CertificatePath should be readable through ResourceHelper
Andrea Cosentino created CAMEL-18873: Summary: Camel-Elasticsearch: CertificatePath should be readable through ResourceHelper Key: CAMEL-18873 URL: https://issues.apache.org/jira/browse/CAMEL-18873 Project: Camel Issue Type: Improvement Components: camel-elasticsearch Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.21.0, 4.0 Instead of specifying a fixed path, we could in this way read from classpath, http etc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18811) camel-ldap - InvalidSearchFilterException: invalid attribute description
[
https://issues.apache.org/jira/browse/CAMEL-18811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17654080#comment-17654080
]
Andrea Cosentino commented on CAMEL-18811:
--
We cannot control the process of retraction. It needs to be propagated from
Mitre to subsystem I guess, but we don't have visibility on that.
> camel-ldap - InvalidSearchFilterException: invalid attribute description
>
>
> Key: CAMEL-18811
> URL: https://issues.apache.org/jira/browse/CAMEL-18811
> Project: Camel
> Issue Type: Bug
> Components: camel-ldap
>Affects Versions: 3.14.7, 3.18.4
> Environment: linux, jdk11, camel-main, camel-ldap, ActiveDirectory
>Reporter: Christian Schubert-Huff
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.14.8, 3.18.5, 3.20.0
>
>
> We updated to camel 3.18.4 and this broke camel-ldap, running against
> ActiveDirectory.
> Filter string is "(CN=USERID)". In 3.18.4, this gets escaped to
> "\28CN=USERID\29" (changed by CAMEL-18696), which does not return a result,
> but instead throws this exception:
> {code:java}
> javax.naming.directory.InvalidSearchFilterException: invalid attribute
> description; remaining name 'OU=Std,OU=User,OU=ORG,DC=ad,DC=example,DC=com'
> at java.naming/com.sun.jndi.ldap.Filter.encodeSimpleFilter(Unknown
> Source)
> at java.naming/com.sun.jndi.ldap.Filter.encodeFilter(Unknown Source)
> at java.naming/com.sun.jndi.ldap.Filter.encodeFilterString(Unknown
> Source)
> at java.naming/com.sun.jndi.ldap.LdapClient.search(Unknown Source)
> at java.naming/com.sun.jndi.ldap.LdapCtx.doSearch(Unknown Source)
> at java.naming/com.sun.jndi.ldap.LdapCtx.searchAux(Unknown Source)
> at java.naming/com.sun.jndi.ldap.LdapCtx.c_search(Unknown Source)
> at
> java.naming/com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(Unknown
> Source)
> at
> java.naming/com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(Unknown
> Source)
> at
> java.naming/com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(Unknown
> Source)
> at
> java.naming/javax.naming.directory.InitialDirContext.search(Unknown Source)
> at
> org.apache.camel.component.ldap.LdapProducer.simpleSearch(LdapProducer.java:129)
> at
> org.apache.camel.component.ldap.LdapProducer.process(LdapProducer.java:83)
> {code}
> The same filter string used to work fine in 3.18.1
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (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:all-tabpanel ] Andrea Cosentino updated CAMEL-18131: - Description: A number of components have the old component extension verification (see aws-s3) - we can migrate that into health-checks. *Components to update (partial table):* |Component|Done| |AWS2-S3|x| |AWS2-ATHENA|x| |AWS2-EKS|x| |AWS2-CW|x| |AWS2-DDB|x| |AWS2-DDBStreams|x| |AWS2-EC2|x| |AWS2-EVENTBRIDGE| | |AWS2-IAM|x| |AWS2-KINESIS|x| |camel-aws-cloudtrail| | |camel-aws-secrets-manager| | |camel-aws-xray| | |camel-aws2-ecs|x| |camel-aws2-lambda| | |camel-aws2-mq| | |camel-aws2-msk| | |camel-aws2-ses| | |camel-aws2-sns|x| |camel-aws2-sqs|x| |camel-aws2-translate| | was: A number of components have the old component extension verification (see aws-s3) - we can migrate that into health-checks. *Components to update (partial table):* |Component|Done| |AWS2-S3|x| |AWS2-ATHENA|x| |AWS2-EKS|x| |AWS2-CW|x| |AWS2-DDB|x| |AWS2-DDBStreams|x| |AWS2-EC2|x| |AWS2-EVENTBRIDGE| | |AWS2-IAM|x| |AWS2-KINESIS|x| |camel-aws-cloudtrail| | |camel-aws-secrets-manager| | |camel-aws-xray| | |camel-aws2-ecs| | |camel-aws2-lambda| | |camel-aws2-mq| | |camel-aws2-msk| | |camel-aws2-ses| | |camel-aws2-sns|x| |camel-aws2-sqs|x| |camel-aws2-translate| | > 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.21.0 > > > A number of components have the old component extension verification (see > aws-s3) - we can migrate that into health-checks. > > *Components to update (partial table):* > |Component|Done| > |AWS2-S3|x| > |AWS2-ATHENA|x| > |AWS2-EKS|x| > |AWS2-CW|x| > |AWS2-DDB|x| > |AWS2-DDBStreams|x| > |AWS2-EC2|x| > |AWS2-EVENTBRIDGE| | > |AWS2-IAM|x| > |AWS2-KINESIS|x| > |camel-aws-cloudtrail| | > |camel-aws-secrets-manager| | > |camel-aws-xray| | > |camel-aws2-ecs|x| > |camel-aws2-lambda| | > |camel-aws2-mq| | > |camel-aws2-msk| | > |camel-aws2-ses| | > |camel-aws2-sns|x| > |camel-aws2-sqs|x| > |camel-aws2-translate| | > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18818) Upgrade to Spring Boot 3.0.0
[ https://issues.apache.org/jira/browse/CAMEL-18818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17647956#comment-17647956 ] Andrea Cosentino edited comment on CAMEL-18818 at 12/15/22 9:31 AM: Spring Boot 3.x support will come with Camel 4.x. Probably in 2023 with some milestone, before a fully supported Camel 4 release. So it's not in the short-term. was (Author: ancosen): Spring Boot 3.x support will come with Camel 4.x. Probably in 2023 with some milestone. > Upgrade to Spring Boot 3.0.0 > > > Key: CAMEL-18818 > URL: https://issues.apache.org/jira/browse/CAMEL-18818 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-spring-boot >Affects Versions: 3.19.0 >Reporter: Clemens Blamauer >Priority: Major > > Dear Camel team, > Is there already a plan/roadmap to upgrade camel-spring-boot to Spring Boot > 3.x? > We are planning to upgrade our microservices to Spring Boot 3 in the course > of next year. As many of them are using Camel, we'd like to consider this in > our roadmap. > Would you please share any plans/high-level roadmap for moving to Spring Boot > 3, if such exist? > Thank you. > Kind regards, > Clemens -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18818) Upgrade to Spring Boot 3.0.0
[ https://issues.apache.org/jira/browse/CAMEL-18818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17647956#comment-17647956 ] Andrea Cosentino commented on CAMEL-18818: -- Spring Boot 3.x support will come with Camel 4.x. Probably in 2023 with some milestone. > Upgrade to Spring Boot 3.0.0 > > > Key: CAMEL-18818 > URL: https://issues.apache.org/jira/browse/CAMEL-18818 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-spring-boot >Affects Versions: 3.19.0 >Reporter: Clemens Blamauer >Priority: Major > > Dear Camel team, > Is there already a plan/roadmap to upgrade camel-spring-boot to Spring Boot > 3.x? > We are planning to upgrade our microservices to Spring Boot 3 in the course > of next year. As many of them are using Camel, we'd like to consider this in > our roadmap. > Would you please share any plans/high-level roadmap for moving to Spring Boot > 3, if such exist? > Thank you. > Kind regards, > Clemens -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18802) camel-base64 - Optional properties: if encoded the optional doesn't have any effect
[
https://issues.apache.org/jira/browse/CAMEL-18802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17646077#comment-17646077
]
Andrea Cosentino commented on CAMEL-18802:
--
My bad. Thanks for this.
> camel-base64 - Optional properties: if encoded the optional doesn't have any
> effect
> ---
>
> Key: CAMEL-18802
> URL: https://issues.apache.org/jira/browse/CAMEL-18802
> Project: Camel
> Issue Type: Improvement
> Components: camel-base64, camel-core
>Reporter: Andrea Cosentino
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.20.0
>
>
> Suppose you have something like:
> {code:java}
> template:
> from:
> uri: "google-storage://{{bucketNameOrArn}}"
> parameters:
> autoCreateBucket: "{{autoCreateBucket}}"
> serviceAccountKey: "base64:{{serviceAccountKey}}"
> deleteAfterRead: "{{deleteAfterRead}}"
> {code}
> and you want to have serviceAccountKey as optional parameter. If you prefix
> the parameter with '?', like
> {code:java}
> template:
> from:
> uri: "google-storage://{{bucketNameOrArn}}"
> parameters:
> autoCreateBucket: "{{autoCreateBucket}}"
> serviceAccountKey: "base64:{{?serviceAccountKey}}"
> deleteAfterRead: "{{deleteAfterRead}}"
> {code}
> We'll try to encode the value anyway, even if not specified.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18802) camel-base64 - Optional properties: if encoded the optional doesn't have any effect
[
https://issues.apache.org/jira/browse/CAMEL-18802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17646066#comment-17646066
]
Andrea Cosentino commented on CAMEL-18802:
--
This is a slightly modify google-storage-source kamelet, where the service
account key is optional
{code:java}
# ---
# Licensed to the Apache Software Foundation (ASF) under one or more
# contributor license agreements. See the NOTICE file distributed with
# this work for additional information regarding copyright ownership.
# The ASF licenses this file to You under the Apache License, Version 2.0
# (the "License"); you may not use this file except in compliance with
# the License. You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# ---
apiVersion: camel.apache.org/v1alpha1
kind: Kamelet
metadata:
name: google-storage-source
annotations:
camel.apache.org/kamelet.support.level: "Stable"
camel.apache.org/catalog.version: "main-SNAPSHOT"
camel.apache.org/kamelet.icon:
"data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiBoZWlnaHQ9IjgwMCIgd2lkdGg9IjEyMDAiIHZpZXdCb3g9Ii0xOS4yMDAxNSAtMjguNDgzIDE2Ni40MDEzIDE3MC44OTgiPjxnIHRyYW5zZm9ybT0idHJhbnNsYXRlKDAgLTcuMDM0KSI+PGxpbmVhckdyYWRpZW50IHkyPSIxMjAuNzg5IiB4Mj0iNjQiIHkxPSI3LjAzNCIgeDE9IjY0IiBncmFkaWVudFVuaXRzPSJ1c2VyU3BhY2VPblVzZSIgaWQ9ImEiPjxzdG9wIG9mZnNldD0iMCIgc3RvcC1jb2xvcj0iIzQzODdmZCIvPjxzdG9wIG9mZnNldD0iMSIgc3RvcC1jb2xvcj0iIzQ2ODNlYSIvPjwvbGluZWFyR3JhZGllbnQ+PHBhdGggZD0iTTI3Ljc5IDExNS4yMTdMMS41NCA2OS43NDlhMTEuNDk5IDExLjQ5OSAwIDAxMC0xMS40OTlsMjYuMjUtNDUuNDY3YTExLjUgMTEuNSAwIDAxOS45Ni01Ljc1aDUyLjVhMTEuNSAxMS41IDAgMDE5Ljk1OSA1Ljc1bDI2LjI1IDQ1LjQ2N2ExMS40OTkgMTEuNDk5IDAgMDEwIDExLjVsLTI2LjI1IDQ1LjQ2NmExMS41IDExLjUgMCAwMS05Ljk1OSA1Ljc1aC01Mi41YTExLjQ5OSAxMS40OTkgMCAwMS05Ljk2LTUuNzV6IiBmaWxsPSJ1cmwoI2EpIi8+PC9nPjxnIHRyYW5zZm9ybT0idHJhbnNsYXRlKDAgLTcuMDM0KSI+PGRlZnM+PHBhdGggZD0iTTI3Ljc5MSAxMTUuMjE3TDEuNTQxIDY5Ljc0OWExMS40OTkgMTEuNDk5IDAgMDEwLTExLjQ5OWwyNi4yNS00NS40NjdhMTEuNDk5IDExLjQ5OSAwIDAxOS45NTktNS43NWg1Mi41YTExLjUgMTEuNSAwIDAxOS45NiA1Ljc1bDI2LjI1IDQ1LjQ2N2ExMS40OTkgMTEuNDk5IDAgMDEwIDExLjVsLTI2LjI1IDQ1LjQ2NmExMS40OTkgMTEuNDk5IDAgMDEtOS45NiA1Ljc1aC01Mi41YTExLjQ5OSAxMS40OTkgMCAwMS05Ljk1OS01Ljc1eiIgaWQ9ImIiLz48L2RlZnM+PGNsaXBQYXRoIGlkPSJjIj48dXNlIGhlaWdodD0iMTAwJSIgd2lkdGg9IjEwMCUiIHhsaW5rOmhyZWY9IiNiIiBvdmVyZmxvdz0idmlzaWJsZSIvPjwvY2xpcFBhdGg+PHBhdGggY2xpcC1wYXRoPSJ1cmwoI2MpIiBvcGFjaXR5PSIuMDciIGQ9Ik00OS4zMTMgNTMuODc1bC03LjAxIDYuOTkgNS45NTcgNS45NTgtNS44OTggMTAuNDc2IDQ0LjYzNSA0NC42MzYgMTAuODE2LjAwMkwxMTguOTM2IDg0IDg1LjQ4OSA1MC41NXoiLz48L2c+PHBhdGggZD0iTTg0LjcgNDMuMjM2SDQzLjI2NGMtLjY2NyAwLTEuMjEyLjU0Ni0xLjIxMiAxLjIxNHY4LjU2NmMwIC42NjYuNTQ2IDEuMjEyIDEuMjEyIDEuMjEySDg0LjdjLjY2NyAwIDEuMjEzLS41NDYgMS4yMTMtMS4yMTJ2LTguNTY4YzAtLjY2Ni0uNTQ1LTEuMjEzLTEuMjEyLTEuMjEzbS02LjQxNiA3Ljk3NmEyLjQ4NCAyLjQ4NCAwIDAxLTIuNDc3LTIuNDggMi40NzUgMi40NzUgMCAwMTIuNDc3LTIuNDc3YzEuMzcgMCAyLjQ4IDEuMTAzIDIuNDggMi40NzdhMi40OCAyLjQ4IDAgMDEtMi40OCAyLjQ4bTYuNDE1IDguNDkxbC00MS40MzYuMDAyYy0uNjY3IDAtMS4yMTIuNTQ2LTEuMjEyIDEuMjE0djguNTY1YzAgLjY2Ni41NDYgMS4yMTMgMS4yMTIgMS4yMTNIODQuN2MuNjY3IDAgMS4yMTMtLjU0NyAxLjIxMy0xLjIxM3YtOC41NjdjMC0uNjY2LS41NDUtMS4yMTQtMS4yMTItMS4yMTRtLTYuNDE2IDcuOTc2YTIuNDgzIDIuNDgzIDAgMDEtMi40NzctMi40OCAyLjQ3NSAyLjQ3NSAwIDAxMi40NzctMi40NzcgMi40OCAyLjQ4IDAgMTEwIDQuOTU2IiBmaWxsPSIjZmZmIi8+PC9zdmc+"
camel.apache.org/provider: "Apache Software Foundation"
camel.apache.org/kamelet.group: "Google Storage"
labels:
camel.apache.org/kamelet.type: "source"
spec:
definition:
title: "Google Storage Source"
description: |-
Consume objects from Google Cloud Storage.
You must encode the `serviceAccountKey` property before you pass it as a
parameter.
required:
- bucketNameOrArn
type: object
properties:
bucketNameOrArn:
title: Bucket Name Or ARN
description: The Google Cloud Storage bucket name or Bucket Amazon
Resource Name (ARN).
type: string
serviceAccountKey:
title: Service Account Key
description: The service account key to use as credentials for Google
Cloud Storage access. You must encode this value in base64.
type: binary
x-descriptors:
- urn:camel:group:credentials
deleteAfterRead:
title: Auto-delete Objects
description: Specifies to delete objects after consuming them.
type: boo
[jira] [Commented] (CAMEL-18802) camel-base64 - Optional properties: if encoded the optional doesn't have any effect
[
https://issues.apache.org/jira/browse/CAMEL-18802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17646063#comment-17646063
]
Andrea Cosentino commented on CAMEL-18802:
--
In Kamelets through camel-jbang it doesn't seem to work.
{code:java}
org.apache.camel.FailedToStartRouteException: Failed to start route
google-storage-source-1 because of null
at
org.apache.camel.impl.engine.RouteService.warmUp(RouteService.java:123)
at
org.apache.camel.impl.engine.InternalRouteStartupManager.doWarmUpRoutes(InternalRouteStartupManager.java:306)
at
org.apache.camel.impl.engine.InternalRouteStartupManager.safelyStartRouteServices(InternalRouteStartupManager.java:189)
at
org.apache.camel.impl.engine.InternalRouteStartupManager.doStartOrResumeRoutes(InternalRouteStartupManager.java:147)
at
org.apache.camel.impl.engine.AbstractCamelContext.doStartCamel(AbstractCamelContext.java:3425)
at
org.apache.camel.impl.engine.AbstractCamelContext.doStartContext(AbstractCamelContext.java:3094)
at
org.apache.camel.impl.engine.AbstractCamelContext.doStart(AbstractCamelContext.java:3049)
at
org.apache.camel.support.service.BaseService.start(BaseService.java:119)
at
org.apache.camel.impl.engine.AbstractCamelContext.start(AbstractCamelContext.java:2698)
at
org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:262)
at org.apache.camel.main.KameletMain.doStart(KameletMain.java:274)
at
org.apache.camel.support.service.BaseService.start(BaseService.java:119)
at org.apache.camel.dsl.jbang.core.commands.Run.run(Run.java:560)
at org.apache.camel.dsl.jbang.core.commands.Run.call(Run.java:208)
at org.apache.camel.dsl.jbang.core.commands.Run.call(Run.java:75)
at picocli.CommandLine.executeUserObject(CommandLine.java:2041)
at picocli.CommandLine.access$1500(CommandLine.java:148)
at
picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2461)
at picocli.CommandLine$RunLast.handle(CommandLine.java:2453)
at picocli.CommandLine$RunLast.handle(CommandLine.java:2415)
at
picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2273)
at picocli.CommandLine$RunLast.execute(CommandLine.java:2417)
at picocli.CommandLine.execute(CommandLine.java:2170)
at
org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:129)
at main.CamelJBang.main(CamelJBang.java:36)
Caused by: org.apache.camel.RuntimeCamelException:
java.io.FileNotFoundException: Cannot find resource: ?serviceAccountKey for
URI: ?serviceAccountKey
at
org.apache.camel.RuntimeCamelException.wrapRuntimeException(RuntimeCamelException.java:66)
at
org.apache.camel.support.service.BaseService.doFail(BaseService.java:413)
at
org.apache.camel.support.service.BaseService.fail(BaseService.java:342)
at
org.apache.camel.support.service.BaseService.start(BaseService.java:132)
at
org.apache.camel.support.service.ServiceHelper.startService(ServiceHelper.java:113)
at
org.apache.camel.impl.engine.RouteService.doWarmUp(RouteService.java:184)
at
org.apache.camel.impl.engine.RouteService.warmUp(RouteService.java:121)
... 24 more
Caused by: java.io.FileNotFoundException: Cannot find resource:
?serviceAccountKey for URI: ?serviceAccountKey
at
org.apache.camel.support.ResourceHelper.resolveMandatoryResourceAsInputStream(ResourceHelper.java:115)
at
org.apache.camel.component.google.storage.GoogleCloudStorageConnectionFactory.create(GoogleCloudStorageConnectionFactory.java:39)
at
org.apache.camel.component.google.storage.GoogleCloudStorageEndpoint.doStart(GoogleCloudStorageEndpoint.java:75)
at
org.apache.camel.support.service.BaseService.start(BaseService.java:119)
... 27 more
{code}
> camel-base64 - Optional properties: if encoded the optional doesn't have any
> effect
> ---
>
> Key: CAMEL-18802
> URL: https://issues.apache.org/jira/browse/CAMEL-18802
> Project: Camel
> Issue Type: Improvement
> Components: camel-base64, camel-core
>Reporter: Andrea Cosentino
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.20.0
>
>
> Suppose you have something like:
> {code:java}
> template:
> from:
> uri: "google-storage://{{bucketNameOrArn}}"
> parameters:
> autoCreateBucket: "{{autoCreateBucket}}"
> serviceAccountKey: "base64:{{serviceAccountKey}}"
> deleteAfterRead: "{{deleteAfterRead}}"
> {code}
> and you want to have serviceAccountKey as optional parameter. If you prefix
> the parameter wit
[jira] [Updated] (CAMEL-18804) Camel-SFTP: Host key type ED25519 not supported
[ https://issues.apache.org/jira/browse/CAMEL-18804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-18804: - Summary: Camel-SFTP: Host key type ED25519 not supported (was: Host key type ED25519 not supported) > Camel-SFTP: Host key type ED25519 not supported > --- > > Key: CAMEL-18804 > URL: https://issues.apache.org/jira/browse/CAMEL-18804 > Project: Camel > Issue Type: Bug > Components: camel-sftp >Affects Versions: 3.14.5, 3.18.2 >Reporter: Maarten Donderwinkel >Priority: Major > > According to the documentation for the camel-sftp component it's possible to > set a server_host_key with the value ed25519. However that algorithm is not > available with Jsch. > As a result the documentation is confusing as it's proposing options that are > not available. > When trying the parameter it will ignore ed25519 as jschProposal. > > Please change at least the documentation to list: > ssh-dss,ssh-rsa,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521 > Perhaps look into using the fork of jsch or other means to allow for ED25519 > as algorithm. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18802) Optional properties: if encoded the optional doesn't have any effect
Andrea Cosentino created CAMEL-18802:
Summary: Optional properties: if encoded the optional doesn't have
any effect
Key: CAMEL-18802
URL: https://issues.apache.org/jira/browse/CAMEL-18802
Project: Camel
Issue Type: New Feature
Reporter: Andrea Cosentino
Suppose you have something like:
{code:java}
template:
from:
uri: "google-storage://{{bucketNameOrArn}}"
parameters:
autoCreateBucket: "{{autoCreateBucket}}"
serviceAccountKey: "base64:{{serviceAccountKey}}"
deleteAfterRead: "{{deleteAfterRead}}"
{code}
and you want to have serviceAccountKey as optional parameter. If you prefix the
parameter with '?', like
{code:java}
template:
from:
uri: "google-storage://{{bucketNameOrArn}}"
parameters:
autoCreateBucket: "{{autoCreateBucket}}"
serviceAccountKey: "base64:{{?serviceAccountKey}}"
deleteAfterRead: "{{deleteAfterRead}}"
{code}
We'll try to encode the value anyway, even if not specified.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18496) Remove deprecated components
[ https://issues.apache.org/jira/browse/CAMEL-18496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644260#comment-17644260 ] Andrea Cosentino commented on CAMEL-18496: -- Yeah, +1 > Remove deprecated components > > > Key: CAMEL-18496 > URL: https://issues.apache.org/jira/browse/CAMEL-18496 > Project: Camel > Issue Type: Task >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 3.x > > > * camel-ahc: CAMEL-17667 > * camel-ahc-ws: CAMEL-17667 > * camel-dozer: CAMEL-18455 > * camel-cmis: https://issues.apache.org/jira/browse/CAMEL-18495 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18743) camel-jbang - Command to see only if everything is okay or there has been a failure
[ https://issues.apache.org/jira/browse/CAMEL-18743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18743. -- Resolution: Fixed > camel-jbang - Command to see only if everything is okay or there has been a > failure > --- > > Key: CAMEL-18743 > URL: https://issues.apache.org/jira/browse/CAMEL-18743 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.20.0 > > > Finding a good name is hard, maybe > camel get count=total,error > 1,0 > camel get count=total,error > 2,1 > So this gets a count of total messages processed, failed messages > The idea is a way to quickly tell from tooling that Camel processed messaged > and that there was no errors. And we need to ensure that it does not say 0 > due to nothing has been processed at all, so we need to have output of total > + error. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18743) camel-jbang - Command to see only if everything is okay or there has been a failure
[ https://issues.apache.org/jira/browse/CAMEL-18743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-18743: Assignee: Andrea Cosentino > camel-jbang - Command to see only if everything is okay or there has been a > failure > --- > > Key: CAMEL-18743 > URL: https://issues.apache.org/jira/browse/CAMEL-18743 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.20.0 > > > Finding a good name is hard, maybe > camel get count=total,error > 1,0 > camel get count=total,error > 2,1 > So this gets a count of total messages processed, failed messages > The idea is a way to quickly tell from tooling that Camel processed messaged > and that there was no errors. And we need to ensure that it does not say 0 > due to nothing has been processed at all, so we need to have output of total > + error. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18773) camel-google-pubsub - Do not use dot in header keys
[ https://issues.apache.org/jira/browse/CAMEL-18773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18773. -- Resolution: Fixed > camel-google-pubsub - Do not use dot in header keys > --- > > Key: CAMEL-18773 > URL: https://issues.apache.org/jira/browse/CAMEL-18773 > Project: Camel > Issue Type: Improvement > Components: camel-google-pubsub >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.20.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18773) camel-google-pubsub - Do not use dot in header keys
[ https://issues.apache.org/jira/browse/CAMEL-18773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-18773: Assignee: Andrea Cosentino > camel-google-pubsub - Do not use dot in header keys > --- > > Key: CAMEL-18773 > URL: https://issues.apache.org/jira/browse/CAMEL-18773 > Project: Camel > Issue Type: Improvement > Components: camel-google-pubsub >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18773) camel-google-pubsub - Do not use dot in header keys
[ https://issues.apache.org/jira/browse/CAMEL-18773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-18773: - Fix Version/s: 3.20.0 > camel-google-pubsub - Do not use dot in header keys > --- > > Key: CAMEL-18773 > URL: https://issues.apache.org/jira/browse/CAMEL-18773 > Project: Camel > Issue Type: Improvement > Components: camel-google-pubsub >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.20.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18777) Camel-Google-Storage: getObject Producer operation should place the object content in the body and populating headers with other info
[ https://issues.apache.org/jira/browse/CAMEL-18777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18777. -- Resolution: Fixed > Camel-Google-Storage: getObject Producer operation should place the object > content in the body and populating headers with other info > - > > Key: CAMEL-18777 > URL: https://issues.apache.org/jira/browse/CAMEL-18777 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.20.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18777) Camel-Google-Storage: getObject Producer operation should place the object content in the body and populating headers with other info
Andrea Cosentino created CAMEL-18777: Summary: Camel-Google-Storage: getObject Producer operation should place the object content in the body and populating headers with other info Key: CAMEL-18777 URL: https://issues.apache.org/jira/browse/CAMEL-18777 Project: Camel Issue Type: Improvement Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.20.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18746) camel-spring-boot 3.18.3 release missing debezium-db2-starter / debezium-oracle-starter
[ https://issues.apache.org/jira/browse/CAMEL-18746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-18746: - Fix Version/s: 3.18.4 3.20.0 > camel-spring-boot 3.18.3 release missing debezium-db2-starter / > debezium-oracle-starter > --- > > Key: CAMEL-18746 > URL: https://issues.apache.org/jira/browse/CAMEL-18746 > Project: Camel > Issue Type: Bug > Components: camel-spring-boot, camel-spring-boot-starters >Affects Versions: 3.18.3 >Reporter: Thomas Cunningham >Priority: Major > Fix For: 3.18.4, 3.20.0 > > > camel-spring-boot-3.18.x branch contains a debezium-db2-starter and a > debezium-oracle-starter : > [https://github.com/apache/camel-spring-boot/tree/camel-spring-boot-3.18.x/components-starter/camel-debezium-db2-starter] > [https://github.com/apache/camel-spring-boot/tree/camel-spring-boot-3.18.x/components-starter/camel-debezium-oracle-starter] > It looks like these have not been added as modules to components-starter: > [https://github.com/apache/camel-spring-boot/blob/main/components-starter/pom.xml] > Should they be? > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18746) camel-spring-boot 3.18.3 release missing debezium-db2-starter / debezium-oracle-starter
[ https://issues.apache.org/jira/browse/CAMEL-18746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637724#comment-17637724 ] Andrea Cosentino commented on CAMEL-18746: -- Yes, they should be there. > camel-spring-boot 3.18.3 release missing debezium-db2-starter / > debezium-oracle-starter > --- > > Key: CAMEL-18746 > URL: https://issues.apache.org/jira/browse/CAMEL-18746 > Project: Camel > Issue Type: Bug > Components: camel-spring-boot, camel-spring-boot-starters >Affects Versions: 3.18.3 >Reporter: Thomas Cunningham >Priority: Major > Fix For: 3.18.4, 3.20.0 > > > camel-spring-boot-3.18.x branch contains a debezium-db2-starter and a > debezium-oracle-starter : > [https://github.com/apache/camel-spring-boot/tree/camel-spring-boot-3.18.x/components-starter/camel-debezium-db2-starter] > [https://github.com/apache/camel-spring-boot/tree/camel-spring-boot-3.18.x/components-starter/camel-debezium-oracle-starter] > It looks like these have not been added as modules to components-starter: > [https://github.com/apache/camel-spring-boot/blob/main/components-starter/pom.xml] > Should they be? > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18743) camel-jbang - Command to see only if everything is okay or there has been a failure
[ https://issues.apache.org/jira/browse/CAMEL-18743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637121#comment-17637121 ] Andrea Cosentino commented on CAMEL-18743: -- This would be super helpful here for example: https://github.com/apache/camel-kamelets/tree/main/it-tests > camel-jbang - Command to see only if everything is okay or there has been a > failure > --- > > Key: CAMEL-18743 > URL: https://issues.apache.org/jira/browse/CAMEL-18743 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Priority: Minor > Fix For: 3.20.0 > > > Finding a good name is hard, maybe > camel get count=total,error > 1,0 > camel get count=total,error > 2,1 > So this gets a count of total messages processed, failed messages > The idea is a way to quickly tell from tooling that Camel processed messaged > and that there was no errors. And we need to ensure that it does not say 0 > due to nothing has been processed at all, so we need to have output of total > + error. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18722) Camel AWS2 S3 doesn't handle metadata correctly
[ https://issues.apache.org/jira/browse/CAMEL-18722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18722. -- Resolution: Fixed > Camel AWS2 S3 doesn't handle metadata correctly > --- > > Key: CAMEL-18722 > URL: https://issues.apache.org/jira/browse/CAMEL-18722 > Project: Camel > Issue Type: Bug > Components: camel-aws2 >Affects Versions: 3.18.2, 3.18.3 >Reporter: Henrik Karlsson >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.18.4, 3.20.0 > > > When storing files to AWS S3 metadata like Content-Disposition isn't handled > correctly by the camel-aws2-s3 component. It should be stored as > 'Content-Disposition' but is stored as 'x-amz-meta-content-disposition'. > Content-Type is stored as both 'Content-Type' and 'x-amz-meta-content-type'. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18726) Merge camel-k-runtime into camel-quarkus
[ https://issues.apache.org/jira/browse/CAMEL-18726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17635886#comment-17635886 ] Andrea Cosentino commented on CAMEL-18726: -- I think this should go in Camel-Quarkus issues and camel-k issues, not in the Camel JIRA. It's not really related to Camel at all. > Merge camel-k-runtime into camel-quarkus > > > Key: CAMEL-18726 > URL: https://issues.apache.org/jira/browse/CAMEL-18726 > Project: Camel > Issue Type: Task >Reporter: Claudio Miranda >Assignee: Claudio Miranda >Priority: Major > > Migrate all camel-k-runtime quarkus extensions into camel-quarkus project. > camel-k-runtime used to host some camel components and its quarkus extensions > suitable for camel-k project, however today all camel components are already > in camel, only the quarkus extensions remained in camel-k-runtime project. > It seems appropriate to move all camel-k-runtime quarkus extensions into > camel-quarkus project. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18723) How can i retrieve file name when SftpException Occured
[ https://issues.apache.org/jira/browse/CAMEL-18723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18723. -- Resolution: Invalid Please ask on Zulip or user mailing list. Jira is for issues. > How can i retrieve file name when SftpException Occured > --- > > Key: CAMEL-18723 > URL: https://issues.apache.org/jira/browse/CAMEL-18723 > Project: Camel > Issue Type: Bug > Components: camel-ftp >Affects Versions: 3.14.2 >Reporter: Kouame >Priority: Minor > > Hi all, > I want to know if it's possible to get the file name when error occured > during local copy file in SftpOperations. > I have put an OnException but in the processor, i can't get the name of file > because the message has been changed during > GenericFileOperationFailedException -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18722) Camel AWS2 S3 doesn't handle metadata correctly
[ https://issues.apache.org/jira/browse/CAMEL-18722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-18722: - Fix Version/s: 3.18.4 3.20.0 > Camel AWS2 S3 doesn't handle metadata correctly > --- > > Key: CAMEL-18722 > URL: https://issues.apache.org/jira/browse/CAMEL-18722 > Project: Camel > Issue Type: Bug > Components: camel-aws2 >Affects Versions: 3.18.2, 3.18.3 >Reporter: Henrik Karlsson >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.18.4, 3.20.0 > > > When storing files to AWS S3 metadata like Content-Disposition isn't handled > correctly by the camel-aws2-s3 component. It should be stored as > 'Content-Disposition' but is stored as 'x-amz-meta-content-disposition'. > Content-Type is stored as both 'Content-Type' and 'x-amz-meta-content-type'. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18722) Camel AWS2 S3 doesn't handle metadata correctly
[ https://issues.apache.org/jira/browse/CAMEL-18722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17633996#comment-17633996 ] Andrea Cosentino commented on CAMEL-18722: -- I'll have a look. If you want to open a PR please do. > Camel AWS2 S3 doesn't handle metadata correctly > --- > > Key: CAMEL-18722 > URL: https://issues.apache.org/jira/browse/CAMEL-18722 > Project: Camel > Issue Type: Bug > Components: camel-aws2 >Affects Versions: 3.18.2, 3.18.3 >Reporter: Henrik Karlsson >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.18.4, 3.20.0 > > > When storing files to AWS S3 metadata like Content-Disposition isn't handled > correctly by the camel-aws2-s3 component. It should be stored as > 'Content-Disposition' but is stored as 'x-amz-meta-content-disposition'. > Content-Type is stored as both 'Content-Type' and 'x-amz-meta-content-type'. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18722) Camel AWS2 S3 doesn't handle metadata correctly
[ https://issues.apache.org/jira/browse/CAMEL-18722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-18722: Assignee: Andrea Cosentino > Camel AWS2 S3 doesn't handle metadata correctly > --- > > Key: CAMEL-18722 > URL: https://issues.apache.org/jira/browse/CAMEL-18722 > Project: Camel > Issue Type: Bug > Components: camel-aws2 >Affects Versions: 3.18.2, 3.18.3 >Reporter: Henrik Karlsson >Assignee: Andrea Cosentino >Priority: Major > > When storing files to AWS S3 metadata like Content-Disposition isn't handled > correctly by the camel-aws2-s3 component. It should be stored as > 'Content-Disposition' but is stored as 'x-amz-meta-content-disposition'. > Content-Type is stored as both 'Content-Type' and 'x-amz-meta-content-type'. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-14831) Create a Camel-rocketmq component
[ https://issues.apache.org/jira/browse/CAMEL-14831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17633239#comment-17633239 ] Andrea Cosentino commented on CAMEL-14831: -- It needs to be updated to camel 3.20.0-SNAPSHOT. Can you please open a draft PR? Thanks. > Create a Camel-rocketmq component > - > > Key: CAMEL-14831 > URL: https://issues.apache.org/jira/browse/CAMEL-14831 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Priority: Minor > Fix For: Future > > > [https://rocketmq.apache.org/] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-16273) Camel-google-* cloud components: Make the serviceAccountKey explicitly configurable
[ https://issues.apache.org/jira/browse/CAMEL-16273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-16273. -- Resolution: Duplicate > Camel-google-* cloud components: Make the serviceAccountKey explicitly > configurable > --- > > Key: CAMEL-16273 > URL: https://issues.apache.org/jira/browse/CAMEL-16273 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.20.0 > > > Only google-storage provide this option, the others need to have an > environment variable set, as google cloud client support by default -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-16273) Camel-google-* cloud components: Make the serviceAccountKey explicitly configurable
[ https://issues.apache.org/jira/browse/CAMEL-16273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17631041#comment-17631041 ] Andrea Cosentino commented on CAMEL-16273: -- Yes, let me close this. > Camel-google-* cloud components: Make the serviceAccountKey explicitly > configurable > --- > > Key: CAMEL-16273 > URL: https://issues.apache.org/jira/browse/CAMEL-16273 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.20.0 > > > Only google-storage provide this option, the others need to have an > environment variable set, as google cloud client support by default -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18643) AWS Health Check: Use AwsServiceException instead of SdkClientException for health check
[ https://issues.apache.org/jira/browse/CAMEL-18643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18643. -- Resolution: Fixed > AWS Health Check: Use AwsServiceException instead of SdkClientException for > health check > > > Key: CAMEL-18643 > URL: https://issues.apache.org/jira/browse/CAMEL-18643 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.20.0 > > > So we could set error code and status code in the health check details. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18682) Camel-Plc4x: Add a Spring Boot starter
[ https://issues.apache.org/jira/browse/CAMEL-18682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18682. -- Resolution: Fixed > Camel-Plc4x: Add a Spring Boot starter > -- > > Key: CAMEL-18682 > URL: https://issues.apache.org/jira/browse/CAMEL-18682 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.20.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (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:all-tabpanel ] Andrea Cosentino updated CAMEL-18131: - Description: A number of components have the old component extension verification (see aws-s3) - we can migrate that into health-checks. *Components to update (partial table):* |Component|Done| |AWS2-S3|x| |AWS2-ATHENA|x| |AWS2-EKS|x| |AWS2-CW|x| |AWS2-DDB|x| |AWS2-DDBStreams|x| |AWS2-EC2|x| |AWS2-EVENTBRIDGE| | |AWS2-IAM| | |AWS2-KINESIS|x| was: A number of components have the old component extension verification (see aws-s3) - we can migrate that into health-checks. *Components to update (partial table):* |Component|Done| |AWS2-S3|x| |AWS2-ATHENA|x| |AWS2-EKS|x| |AWS2-CW|x| |AWS2-DDB|x| |AWS2-DDBStreams| | |AWS2-EC2|x| |AWS2-EVENTBRIDGE| | |AWS2-IAM| | |AWS2-KINESIS|x| > 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.20.0 > > > A number of components have the old component extension verification (see > aws-s3) - we can migrate that into health-checks. > > *Components to update (partial table):* > |Component|Done| > |AWS2-S3|x| > |AWS2-ATHENA|x| > |AWS2-EKS|x| > |AWS2-CW|x| > |AWS2-DDB|x| > |AWS2-DDBStreams|x| > |AWS2-EC2|x| > |AWS2-EVENTBRIDGE| | > |AWS2-IAM| | > |AWS2-KINESIS|x| -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18684) Add Microsoft Exchange Online OAuth2 Mail Authenticator
[
https://issues.apache.org/jira/browse/CAMEL-18684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-18684.
--
Resolution: Fixed
> Add Microsoft Exchange Online OAuth2 Mail Authenticator
> ---
>
> Key: CAMEL-18684
> URL: https://issues.apache.org/jira/browse/CAMEL-18684
> Project: Camel
> Issue Type: Improvement
> Components: camel-mail
>Reporter: Luigi De Masi
>Assignee: Luigi De Masi
>Priority: Minor
> Fix For: 3.18.4, 3.20.0
>
>
> Add an implementation of
> {{org.apache.camel.component.mail.MailAuthenticator}} to facilitate users
> that want to use OAuth2 authentication using Client Credentials Flow.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18684) Add Microsoft Exchange Online OAuth2 Mail Authenticator
[
https://issues.apache.org/jira/browse/CAMEL-18684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-18684:
-
Fix Version/s: 3.18.4
3.20.0
> Add Microsoft Exchange Online OAuth2 Mail Authenticator
> ---
>
> Key: CAMEL-18684
> URL: https://issues.apache.org/jira/browse/CAMEL-18684
> Project: Camel
> Issue Type: Improvement
> Components: camel-mail
>Reporter: Luigi De Masi
>Assignee: Luigi De Masi
>Priority: Minor
> Fix For: 3.18.4, 3.20.0
>
>
> Add an implementation of
> {{org.apache.camel.component.mail.MailAuthenticator}} to facilitate users
> that want to use OAuth2 authentication using Client Credentials Flow.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18621) Vulnerabilities identified with jackson-databind dependency
[ https://issues.apache.org/jira/browse/CAMEL-18621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17629743#comment-17629743 ] Andrea Cosentino commented on CAMEL-18621: -- I do understand everybody wants to avoid static dependency checker to report vulns, but we cannot do everything for everyone. The codebase and ecosystem is big and aligning dependencies everywhere is not as easy as it could seem. > Vulnerabilities identified with jackson-databind dependency > --- > > Key: CAMEL-18621 > URL: https://issues.apache.org/jira/browse/CAMEL-18621 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jackson >Affects Versions: 3.18.2, 3.19.0 >Reporter: Sasikumar Muthukrishnan Sampath >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.20.0 > > > There are two new vulnerabilities identified with jackson-databind > dependency. Please upgrade the jackson dependency version to 2.14.x > [CVE-2022-42003|https://github.com/advisories/GHSA-rgv9-q543-rqg4] > [CVE-2022-42004|https://github.com/advisories/GHSA-rgv9-q543-rqg4]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18621) Vulnerabilities identified with jackson-databind dependency
[ https://issues.apache.org/jira/browse/CAMEL-18621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17629742#comment-17629742 ] Andrea Cosentino edited comment on CAMEL-18621 at 11/7/22 10:30 AM: Using micro release means specify different version of jackson databind wherever we have them. This also means the need to add specific version of jackson databind in all the karaf features using jackson. It's an effort that doesn't worth to be done if the the major release was in the short term, as it was. was (Author: ancosen): Using micro release means specify different version of jackson databind wherever we have them. This also means the need to add specific version of jackson databind in all the karaf features using jackson. It's an effort that doesn't worth to be done if the the major release aws in the short term, as it was. > Vulnerabilities identified with jackson-databind dependency > --- > > Key: CAMEL-18621 > URL: https://issues.apache.org/jira/browse/CAMEL-18621 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jackson >Affects Versions: 3.18.2, 3.19.0 >Reporter: Sasikumar Muthukrishnan Sampath >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.20.0 > > > There are two new vulnerabilities identified with jackson-databind > dependency. Please upgrade the jackson dependency version to 2.14.x > [CVE-2022-42003|https://github.com/advisories/GHSA-rgv9-q543-rqg4] > [CVE-2022-42004|https://github.com/advisories/GHSA-rgv9-q543-rqg4]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18621) Vulnerabilities identified with jackson-databind dependency
[ https://issues.apache.org/jira/browse/CAMEL-18621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17629742#comment-17629742 ] Andrea Cosentino commented on CAMEL-18621: -- Using micro release means specify different version of jackson databind wherever we have them. This also means the need to add specific version of jackson databind in all the karaf features using jackson. It's an effort that doesn't worth to be done if the the major release aws in the short term, as it was. > Vulnerabilities identified with jackson-databind dependency > --- > > Key: CAMEL-18621 > URL: https://issues.apache.org/jira/browse/CAMEL-18621 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jackson >Affects Versions: 3.18.2, 3.19.0 >Reporter: Sasikumar Muthukrishnan Sampath >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.20.0 > > > There are two new vulnerabilities identified with jackson-databind > dependency. Please upgrade the jackson dependency version to 2.14.x > [CVE-2022-42003|https://github.com/advisories/GHSA-rgv9-q543-rqg4] > [CVE-2022-42004|https://github.com/advisories/GHSA-rgv9-q543-rqg4]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18621) Vulnerabilities identified with jackson-databind dependency
[ https://issues.apache.org/jira/browse/CAMEL-18621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18621. -- Resolution: Fixed > Vulnerabilities identified with jackson-databind dependency > --- > > Key: CAMEL-18621 > URL: https://issues.apache.org/jira/browse/CAMEL-18621 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jackson >Affects Versions: 3.18.2, 3.19.0 >Reporter: Sasikumar Muthukrishnan Sampath >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.20.0 > > > There are two new vulnerabilities identified with jackson-databind > dependency. Please upgrade the jackson dependency version to 2.14.x > [CVE-2022-42003|https://github.com/advisories/GHSA-rgv9-q543-rqg4] > [CVE-2022-42004|https://github.com/advisories/GHSA-rgv9-q543-rqg4]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18621) Vulnerabilities identified with jackson-databind dependency
[ https://issues.apache.org/jira/browse/CAMEL-18621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-18621: Assignee: Andrea Cosentino > Vulnerabilities identified with jackson-databind dependency > --- > > Key: CAMEL-18621 > URL: https://issues.apache.org/jira/browse/CAMEL-18621 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jackson >Affects Versions: 3.18.2, 3.19.0 >Reporter: Sasikumar Muthukrishnan Sampath >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.20.0 > > > There are two new vulnerabilities identified with jackson-databind > dependency. Please upgrade the jackson dependency version to 2.14.x > [CVE-2022-42003|https://github.com/advisories/GHSA-rgv9-q543-rqg4] > [CVE-2022-42004|https://github.com/advisories/GHSA-rgv9-q543-rqg4]. -- 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 ] Andrea Cosentino updated CAMEL-17856: - Fix Version/s: 3.20.0 (was: 3.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.20.0 > > > 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] [Resolved] (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 ] Andrea Cosentino resolved CAMEL-17856. -- Resolution: Fixed > 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.20.0 > > > 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-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:all-tabpanel ] Andrea Cosentino updated CAMEL-18131: - Description: A number of components have the old component extension verification (see aws-s3) - we can migrate that into health-checks. *Components to update (partial table):* |Component|Done| |AWS2-S3|x| |AWS2-ATHENA|x| |AWS2-EKS|x| |AWS2-CW|x| |AWS2-DDB|x| |AWS2-DDBStreams| | |AWS2-EC2| | |AWS2-EVENTBRIDGE| | |AWS2-IAM| | |AWS2-KINESIS|x| was: A number of components have the old component extension verification (see aws-s3) - we can migrate that into health-checks. *Components to update (partial table):* |Component|Done| |AWS2-S3|x| |AWS2-ATHENA|x| |AWS2-EKS|x| |AWS2-CW|x| |AWS2-DDB| | |AWS2-EC2| | |AWS2-EVENTBRIDGE| | |AWS2-IAM| | |AWS2-KINESIS|x| > 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.20.0 > > > A number of components have the old component extension verification (see > aws-s3) - we can migrate that into health-checks. > > *Components to update (partial table):* > |Component|Done| > |AWS2-S3|x| > |AWS2-ATHENA|x| > |AWS2-EKS|x| > |AWS2-CW|x| > |AWS2-DDB|x| > |AWS2-DDBStreams| | > |AWS2-EC2| | > |AWS2-EVENTBRIDGE| | > |AWS2-IAM| | > |AWS2-KINESIS|x| -- 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
]
Andrea Cosentino updated CAMEL-18447:
-
Fix Version/s: 3.18.4
> 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.18.4, 3.20.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] [Created] (CAMEL-18682) Camel-Plc4x: Add a Spring Boot starter
Andrea Cosentino created CAMEL-18682: Summary: Camel-Plc4x: Add a Spring Boot starter Key: CAMEL-18682 URL: https://issues.apache.org/jira/browse/CAMEL-18682 Project: Camel Issue Type: New Feature Components: camel-spring-boot Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.20.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18681) Add an example on how to marshal List of JSON files to single AVRO file
[ https://issues.apache.org/jira/browse/CAMEL-18681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18681. -- Resolution: Invalid For request like this you could either use the mailing list or zulip chat. Thanks. > Add an example on how to marshal List of JSON files to single AVRO file > --- > > Key: CAMEL-18681 > URL: https://issues.apache.org/jira/browse/CAMEL-18681 > Project: Camel > Issue Type: Wish > Components: camel-avro >Affects Versions: 3.18.3 > Environment: Ubuntu 18.04 > >Reporter: Andrii Melashchenko >Priority: Minor > > I failed to implement simple route to dump MongoDB Documents queried via > `findAll` query to Avro data format for further usage in AWS Glue (Apache > Hive) + AWS Athena (Trino) as data source. > It will be great if camel team can provide explicit example on how to marshal > List of the Documents to Avro file. > MongoDB -> List -> file.avro (with schema if possible) > Thank you in advance! > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (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:all-tabpanel ] Andrea Cosentino updated CAMEL-18131: - Description: A number of components have the old component extension verification (see aws-s3) - we can migrate that into health-checks. *Components to update (partial table):* |Component|Done| |AWS2-S3|x| |AWS2-ATHENA|x| |AWS2-EKS|x| |AWS2-CW|x| |AWS2-DDB| | |AWS2-EC2| | |AWS2-EVENTBRIDGE| | |AWS2-IAM| | |AWS2-KINESIS|x| was: A number of components have the old component extension verification (see aws-s3) - we can migrate that into health-checks. *Components to update (partial table):* |Component|Done| |AWS2-S3|x| |AWS2-ATHENA|x| |AWS2-EKS|x| |AWS2-CW| | |AWS2-DDB| | |AWS2-EC2| | |AWS2-EVENTBRIDGE| | |AWS2-IAM| | |AWS2-KINESIS|x| > 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.20.0 > > > A number of components have the old component extension verification (see > aws-s3) - we can migrate that into health-checks. > > *Components to update (partial table):* > |Component|Done| > |AWS2-S3|x| > |AWS2-ATHENA|x| > |AWS2-EKS|x| > |AWS2-CW|x| > |AWS2-DDB| | > |AWS2-EC2| | > |AWS2-EVENTBRIDGE| | > |AWS2-IAM| | > |AWS2-KINESIS|x| -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18621) Vulnerabilities identified with jackson-databind dependency
[ https://issues.apache.org/jira/browse/CAMEL-18621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17625279#comment-17625279 ] Andrea Cosentino commented on CAMEL-18621: -- I don't think is a good idea to follow the micro release. It's hard to align in all the runtime. We will update to 2.14 on 3.18 too > Vulnerabilities identified with jackson-databind dependency > --- > > Key: CAMEL-18621 > URL: https://issues.apache.org/jira/browse/CAMEL-18621 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jackson >Affects Versions: 3.18.2, 3.19.0 >Reporter: Sasikumar Muthukrishnan Sampath >Priority: Minor > Fix For: 3.20.0 > > > There are two new vulnerabilities identified with jackson-databind > dependency. Please upgrade the jackson dependency version to 2.14.x > [CVE-2022-42003|https://github.com/advisories/GHSA-rgv9-q543-rqg4] > [CVE-2022-42004|https://github.com/advisories/GHSA-rgv9-q543-rqg4]. -- 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&focusedCommentId=17624980#comment-17624980 ] Andrea Cosentino commented on CAMEL-18131: -- I'm going to fix this situation by adding a guard on the first check, so we'll check if region is set or not in the configuration before running that particular check. Thanks for reporting. > 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.20.0 > > > A number of components have the old component extension verification (see > aws-s3) - we can migrate that into health-checks. > > *Components to update (partial table):* > |Component|Done| > |AWS2-S3|x| > |AWS2-ATHENA|x| > |AWS2-EKS|x| > |AWS2-CW| | > |AWS2-DDB| | > |AWS2-EC2| | > |AWS2-EVENTBRIDGE| | > |AWS2-IAM| | > |AWS2-KINESIS|x| -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18643) AWS Health Check: Use AwsServiceException instead of SdkClientException for health check
Andrea Cosentino created CAMEL-18643: Summary: AWS Health Check: Use AwsServiceException instead of SdkClientException for health check Key: CAMEL-18643 URL: https://issues.apache.org/jira/browse/CAMEL-18643 Project: Camel Issue Type: Improvement Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.20.0 So we could set error code and status code in the health check details. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (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:all-tabpanel ] Andrea Cosentino updated CAMEL-18131: - Description: A number of components have the old component extension verification (see aws-s3) - we can migrate that into health-checks. *Components to update (partial table):* |Component|Done| |AWS2-S3|x| |AWS2-ATHENA|x| |AWS2-EKS| | |AWS2-CW| | |AWS2-DDB| | |AWS2-EC2| | |AWS2-EVENTBRIDGE| | |AWS2-IAM| | IAWS-KINESIS| Done| was: A number of components have the old component extension verification (see aws-s3) - we can migrate that into health-checks. *Components to update (partial table):* |Component|Done| |AWS2-S3|x| |AWS2-ATHENA|x| |AWS2-EKS| | |AWS2-CW| | |AWS2-DDB| | |AWS2-EC2| | |AWS2-EVENTBRIDGE| | |AWS2-IAM| | > 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.20.0 > > > A number of components have the old component extension verification (see > aws-s3) - we can migrate that into health-checks. > > *Components to update (partial table):* > |Component|Done| > |AWS2-S3|x| > |AWS2-ATHENA|x| > |AWS2-EKS| | > |AWS2-CW| | > |AWS2-DDB| | > |AWS2-EC2| | > |AWS2-EVENTBRIDGE| | > |AWS2-IAM| | > IAWS-KINESIS| Done| -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (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:all-tabpanel ] Andrea Cosentino updated CAMEL-18131: - Description: A number of components have the old component extension verification (see aws-s3) - we can migrate that into health-checks. *Components to update (partial table):* |Component|Done| |AWS2-S3|x| |AWS2-ATHENA|x| |AWS2-EKS| | |AWS2-CW| | |AWS2-DDB| | |AWS2-EC2| | |AWS2-EVENTBRIDGE| | |AWS2-IAM| | IAWS-KINESIS| x| | was: A number of components have the old component extension verification (see aws-s3) - we can migrate that into health-checks. *Components to update (partial table):* |Component|Done| |AWS2-S3|x| |AWS2-ATHENA|x| |AWS2-EKS| | |AWS2-CW| | |AWS2-DDB| | |AWS2-EC2| | |AWS2-EVENTBRIDGE| | |AWS2-IAM| | IAWS-KINESIS| Done| > 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.20.0 > > > A number of components have the old component extension verification (see > aws-s3) - we can migrate that into health-checks. > > *Components to update (partial table):* > |Component|Done| > |AWS2-S3|x| > |AWS2-ATHENA|x| > |AWS2-EKS| | > |AWS2-CW| | > |AWS2-DDB| | > |AWS2-EC2| | > |AWS2-EVENTBRIDGE| | > |AWS2-IAM| | > IAWS-KINESIS| x| | -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (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:all-tabpanel ] Andrea Cosentino updated CAMEL-18131: - Description: A number of components have the old component extension verification (see aws-s3) - we can migrate that into health-checks. *Components to update (partial table):* |Component|Done| |AWS2-S3|x| |AWS2-ATHENA|x| |AWS2-EKS| | |AWS2-CW| | |AWS2-DDB| | |AWS2-EC2| | |AWS2-EVENTBRIDGE| | |AWS2-IAM| | |AWS2-KINESIS|x| was: A number of components have the old component extension verification (see aws-s3) - we can migrate that into health-checks. *Components to update (partial table):* |Component|Done| |AWS2-S3|x| |AWS2-ATHENA|x| |AWS2-EKS| | |AWS2-CW| | |AWS2-DDB| | |AWS2-EC2| | |AWS2-EVENTBRIDGE| | |AWS2-IAM| | IAWS-KINESIS| x| | > 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.20.0 > > > A number of components have the old component extension verification (see > aws-s3) - we can migrate that into health-checks. > > *Components to update (partial table):* > |Component|Done| > |AWS2-S3|x| > |AWS2-ATHENA|x| > |AWS2-EKS| | > |AWS2-CW| | > |AWS2-DDB| | > |AWS2-EC2| | > |AWS2-EVENTBRIDGE| | > |AWS2-IAM| | > |AWS2-KINESIS|x| -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18625) Provide an option to pass specific AWS SAML Profile
[
https://issues.apache.org/jira/browse/CAMEL-18625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17620353#comment-17620353
]
Andrea Cosentino commented on CAMEL-18625:
--
We need to add the option to support this and add some cases to the function. I
can work on this.
> Provide an option to pass specific AWS SAML Profile
>
>
> Key: CAMEL-18625
> URL: https://issues.apache.org/jira/browse/CAMEL-18625
> Project: Camel
> Issue Type: New Feature
> Components: camel-aws
>Reporter: Ajithlal
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.20.0
>
>
> Currently there is no option to pass specific AWS SAML profile when I am
> connecting to AWS secret-manager from camel aws vault program.
> I am expecting ,need a option to set aws saml profile name inside
> application.properties file.
> If user is make below configuration
> camel.vault.aws.defaultCredentialsProvider=false
> camel.vault.aws.saml.profileCredentialName=intdev
> then it should connect to aws resource.
> ("{*}intdev{*}" is aws saml profile name."{*}intdev"{*} is not default
> profile )
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
