[jira] [Commented] (CAMEL-18342) camel-core-model - DSL for calling endpoint and set response to header
[ https://issues.apache.org/jira/browse/CAMEL-18342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768333#comment-17768333 ] tanyu commented on CAMEL-18342: --- Hi, Claus. My understanding is after calling the downstream endpoint, we should set the response to the exchange's header,right? > camel-core-model - DSL for calling endpoint and set response to header > -- > > Key: CAMEL-18342 > URL: https://issues.apache.org/jira/browse/CAMEL-18342 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.x > > > Either we add a special language for calling and endpoint, so you can use DSL > today > > > However the name cannot be to as its already taken as a normal EIP. > Or we could have a new EIP > > And the dynamic variant > > And we may need for exchange properties as well (that would mean 4 new EIPs > in the model). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19891) Update Apache CXF versions to mitigate CVE-2022-46364 and CVE-2022-46363
[ https://issues.apache.org/jira/browse/CAMEL-19891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768310#comment-17768310 ] Alan Dávila commented on CAMEL-19891: - Ok, I have sent the PR for camel-3.14.x branch with the CXF upgrade: [https://github.com/apache/camel/pull/11541] > Update Apache CXF versions to mitigate CVE-2022-46364 and CVE-2022-46363 > > > Key: CAMEL-19891 > URL: https://issues.apache.org/jira/browse/CAMEL-19891 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-cxf >Affects Versions: 3.14.9 >Reporter: Alan Dávila >Priority: Minor > Fix For: 3.14.10 > > > h4. > Update Apache CXF versions to mitigate CVE-2022-46364 > _Apache CXF versions prior to 3.4.10 and 3.5.x prior to 3.5.5 is vulnerable > to SSRF while parsing the `href` attribute of `XOP:Include` in MTOM requests. > It allows an attacker to perform SSRF style attacks on webservices that take > at least one parameter of any type._ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-19910) camel-jbang - Export may include hidden files
Claus Ibsen created CAMEL-19910: --- Summary: camel-jbang - Export may include hidden files Key: CAMEL-19910 URL: https://issues.apache.org/jira/browse/CAMEL-19910 Project: Camel Issue Type: Bug Components: camel-jbang Affects Versions: 4.0.1 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 4.0.2, 4.1.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19910) camel-jbang - Export may include hidden files
[ https://issues.apache.org/jira/browse/CAMEL-19910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19910. - Resolution: Fixed > camel-jbang - Export may include hidden files > - > > Key: CAMEL-19910 > URL: https://issues.apache.org/jira/browse/CAMEL-19910 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Affects Versions: 4.0.1 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.0.2, 4.1.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19802) camel-jbang - Add option to exclude files by pattern
[ https://issues.apache.org/jira/browse/CAMEL-19802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19802. - Resolution: Fixed > camel-jbang - Add option to exclude files by pattern > > > Key: CAMEL-19802 > URL: https://issues.apache.org/jira/browse/CAMEL-19802 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.1.0 > > > To make it easier to skip certain files by --exclude=foo* -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19909) camel-catalog: model catalog refers to not-existing DescriptionDefinition javaType
[ https://issues.apache.org/jira/browse/CAMEL-19909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768274#comment-17768274 ] Tomohisa Igarashi commented on CAMEL-19909: --- Sounds like a plan, I submitted a backport PR - https://github.com/apache/camel/pull/11539 > camel-catalog: model catalog refers to not-existing DescriptionDefinition > javaType > -- > > Key: CAMEL-19909 > URL: https://issues.apache.org/jira/browse/CAMEL-19909 > Project: Camel > Issue Type: Task > Components: camel-catalog >Reporter: Tomohisa Igarashi >Assignee: Tomohisa Igarashi >Priority: Minor > Fix For: 4.1.0 > > > from.json model catalog says "description" is of javaType > "org.apache.camel.model.DescriptionDefinition" but the class doesn't exist. > It's just a String. > https://github.com/apache/camel/blob/main/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/models/from.json#L17 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-19802) camel-jbang - Add option to exclude files by pattern
[ https://issues.apache.org/jira/browse/CAMEL-19802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-19802: --- Assignee: Claus Ibsen > camel-jbang - Add option to exclude files by pattern > > > Key: CAMEL-19802 > URL: https://issues.apache.org/jira/browse/CAMEL-19802 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.1.0 > > > To make it easier to skip certain files by --exclude=foo* -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19774) camel-jbang - Rename bind goal to pipe
[ https://issues.apache.org/jira/browse/CAMEL-19774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19774. - Resolution: Fixed > camel-jbang - Rename bind goal to pipe > -- > > Key: CAMEL-19774 > URL: https://issues.apache.org/jira/browse/CAMEL-19774 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.1.0 > > > Camel K renamed KameletBinding to Pipe, and the bind goal is now misleading. > camel bind -> camel pipe > camel pipe -> camel script (shell script) > Update 4.1 upgrade guide in docs also. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19774) camel-jbang - Rename bind goal to pipe
[ https://issues.apache.org/jira/browse/CAMEL-19774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768271#comment-17768271 ] Claus Ibsen commented on CAMEL-19774: - Lets keep the bind name as pipe is a bit unclear what it does. > camel-jbang - Rename bind goal to pipe > -- > > Key: CAMEL-19774 > URL: https://issues.apache.org/jira/browse/CAMEL-19774 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.1.0 > > > Camel K renamed KameletBinding to Pipe, and the bind goal is now misleading. > camel bind -> camel pipe > camel pipe -> camel script (shell script) > Update 4.1 upgrade guide in docs also. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-19774) camel-jbang - Rename bind goal to pipe
[ https://issues.apache.org/jira/browse/CAMEL-19774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-19774: --- Assignee: Claus Ibsen > camel-jbang - Rename bind goal to pipe > -- > > Key: CAMEL-19774 > URL: https://issues.apache.org/jira/browse/CAMEL-19774 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.1.0 > > > Camel K renamed KameletBinding to Pipe, and the bind goal is now misleading. > camel bind -> camel pipe > camel pipe -> camel script (shell script) > Update 4.1 upgrade guide in docs also. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-17315) Create an AWS Redshift Data Component
[ https://issues.apache.org/jira/browse/CAMEL-17315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768270#comment-17768270 ] Andrea Cosentino commented on CAMEL-17315: -- Yes, we do > Create an AWS Redshift Data Component > - > > Key: CAMEL-17315 > URL: https://issues.apache.org/jira/browse/CAMEL-17315 > Project: Camel > Issue Type: New Feature > Components: camel-aws2 >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.1.0 > > > In this way we can create a specific component in camel for talking with a > Redshift cluster and execute queries against it. > This is a different client from the redshift one: the latter is the client to > create and manage Redshift clusters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-17148) camel-health - Allow to configure to auto stop routes after X failed health-checks
[ https://issues.apache.org/jira/browse/CAMEL-17148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-17148: Fix Version/s: 4.2.0 (was: 4.1.0) > camel-health - Allow to configure to auto stop routes after X failed > health-checks > -- > > Key: CAMEL-17148 > URL: https://issues.apache.org/jira/browse/CAMEL-17148 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.2.0 > > > It can be desireable to make it possible to configure Camel to automatic stop > routes that are un-healthy after they have failed for X times in a row or Y > period (time). > There can be situations where a route will attempt to poll new messages from > some external system, and that keeps failing (networking issues, remote > server error). > Some consumers are scheduled so you can configure them to backoff, but there > is no general configuration for such thing. > Instead we can either make it possible to configure this via health-check on > the route, so this can control the route. > Or we can enhance the route controller (default and supervising) to do this. > However this is maybe a little bit tricker as they are designed to be only > used during bootstrap and starting the routes. After routes are started then > they are no longer in use. > Using health-check seems better as you already have settings for thresholds > to setup how many X in row to regard as UP or DOWN. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-17315) Create an AWS Redshift Data Component
[ https://issues.apache.org/jira/browse/CAMEL-17315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768269#comment-17768269 ] Claus Ibsen commented on CAMEL-17315: - Did we recently add a redshift component? > Create an AWS Redshift Data Component > - > > Key: CAMEL-17315 > URL: https://issues.apache.org/jira/browse/CAMEL-17315 > Project: Camel > Issue Type: New Feature > Components: camel-aws2 >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.1.0 > > > In this way we can create a specific component in camel for talking with a > Redshift cluster and execute queries against it. > This is a different client from the redshift one: the latter is the client to > create and manage Redshift clusters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-16064) camel-kafka - Add batching consumer
[ https://issues.apache.org/jira/browse/CAMEL-16064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-16064: Fix Version/s: 4.2.0 (was: 4.1.0) > camel-kafka - Add batching consumer > --- > > Key: CAMEL-16064 > URL: https://issues.apache.org/jira/browse/CAMEL-16064 > Project: Camel > Issue Type: New Feature > Components: camel-kafka >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.2.0 > > > It would be good to make camel-kafka and camel-vertx-kafka consumer able to > batch together N messages via aggregation strategy as a single outgoing > exchange. The batch should support group size, and timeout. > Something that was in the sjms-batch component. > The batching should use the same KafkaConsumer instance and defer the commit > till the batching has been done. This requires manual offset commit by the > consumer. > The use-case has been discussed on the chat at > https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/kafka.20and.20batching -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-16976) HealthCheck - Rules for failing if a consumer failed polling N messages in a row
[ https://issues.apache.org/jira/browse/CAMEL-16976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-16976: Fix Version/s: 4.2.0 (was: 4.1.0) > HealthCheck - Rules for failing if a consumer failed polling N messages in a > row > > > Key: CAMEL-16976 > URL: https://issues.apache.org/jira/browse/CAMEL-16976 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.2.0 > > > The health checks > https://camel.apache.org/manual/latest/health-check.html > For routes with failure thresholds etc are currently for readiness checks, eg > when starting up the routes. > However after this fact, then at runtime, we may want to be able to say that > if a route consumer have failed X times in a row, then its unhealthy. And to > filter by exception and whatnot. So this can get a bit tricky, but we may > want to have some SPI interface that end users can implement for custom logic. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-16501) camel-jpa - Avoid using EntityManager from header by default
[ https://issues.apache.org/jira/browse/CAMEL-16501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-16501: Fix Version/s: 4.x (was: 4.1.0) > camel-jpa - Avoid using EntityManager from header by default > > > Key: CAMEL-16501 > URL: https://issues.apache.org/jira/browse/CAMEL-16501 > Project: Camel > Issue Type: Improvement > Components: camel-jpa >Reporter: Claus Ibsen >Priority: Minor > Fix For: 4.x > > > See CAMEL-16470 > Historically camel-jpa would lookup from exchange header / property an > EntityManager to use instead of from its own component. This was needed by > jbpm and other 3rd party frameworks that integrated with Camel. > However this causes pain for normal users, where you just want to use the jpa > component out of the box with the JPA EM it has been configured with. And if > you add other jpa components to integrate with other databases, then they > should out of the box use their own EM and so on. This is how JMS, Kafka and > other components work. > So to allow the old behavior, we add a boolean option on the jpa component to > turn on the old style. And then leave it off for new style onwards. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18372) camel-http-streaming - A http consumer that can read an endless stream
[ https://issues.apache.org/jira/browse/CAMEL-18372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18372: Fix Version/s: 4.2.0 (was: 4.1.0) > camel-http-streaming - A http consumer that can read an endless stream > -- > > Key: CAMEL-18372 > URL: https://issues.apache.org/jira/browse/CAMEL-18372 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.2.0 > > > We need a new http consumer component that can do HTTP GET/POST, TLS/SSL et > all and that then connects to a remote HTTP server and does http streaming. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18238) camel-jbang - Used configmaps/secrets should captured
[ https://issues.apache.org/jira/browse/CAMEL-18238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18238: Fix Version/s: 4.x (was: 4.1.0) > camel-jbang - Used configmaps/secrets should captured > - > > Key: CAMEL-18238 > URL: https://issues.apache.org/jira/browse/CAMEL-18238 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.x > > > With CAMEL-18171 then when using configmap or secret then we should capture > these names so we know what are in use. > This can aid for deployment which allows us to generate manifest files that > refer to the used cm/secrets so k8s can mount these automatic. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18695) camel-resume-api: avoid requiring a processor for offset management
[
https://issues.apache.org/jira/browse/CAMEL-18695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18695:
Fix Version/s: 4.x
(was: 4.1.0)
> camel-resume-api: avoid requiring a processor for offset management
> ---
>
> Key: CAMEL-18695
> URL: https://issues.apache.org/jira/browse/CAMEL-18695
> Project: Camel
> Issue Type: Improvement
> Components: camel-resume-api
>Affects Versions: 3.18.3, 3.19.0
>Reporter: Otavio Rodolfo Piske
>Assignee: Otavio Rodolfo Piske
>Priority: Minor
> Fix For: 4.x
>
>
> Currently, in order to update the offsets, the resume API requires a
> processor so that the code can do something like:
>
> {code:java}
> File path = exchange.getMessage().getHeader("CamelFilePath", File.class);
> exchange.getMessage().setHeader(Exchange.OFFSET,
> Resumables.of(path.getParentFile(), path));
> {code}
>
> However, it would be easier if the code could do something like:
> {code:java}
> from("file:{{input.dir}}?noop=true&recursive=true")
> .resumable().configuration(resumeStrategyConfigurationBuilder.withResumeCache(cache)).offset().auto().to("file:{{output.dir}}");{code}
>
> In this case, the adapter would take care of handling the offset updates.
> Alternatively, for slightly more complex scenarios, it could also allow
> something like this:
> {code:java}
> from("file:{{input.dir}}?noop=true&recursive=true").resumable().configuration(resumeStrategyConfigurationBuilder.withResumeCache(cache)).offset().key(header("AHeaderValue")).value(header("SomeOtherHeader").to("file:{{output.dir}}");{code}
>
> Offset updates via processors could still be possible using the existing way.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-17386) camel-main - Developer Mode
[ https://issues.apache.org/jira/browse/CAMEL-17386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-17386: Fix Version/s: 4.2.0 (was: 4.1.0) > camel-main - Developer Mode > --- > > Key: CAMEL-17386 > URL: https://issues.apache.org/jira/browse/CAMEL-17386 > Project: Camel > Issue Type: New Feature > Components: camel-core, camel-main >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.2.0 > > > We should have a developer mode (aka profile) in camel-main which we can use > to startup Camel with the developer console, and other "things" enabled > assists the developer > - developer console > - jmx metrics > - message history > - camel debug > - java flight recorder > - message tracing -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18381) camel-test-infra: implement more singleton services
[ https://issues.apache.org/jira/browse/CAMEL-18381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18381: Fix Version/s: 4.x (was: 4.1.0) > camel-test-infra: implement more singleton services > --- > > Key: CAMEL-18381 > URL: https://issues.apache.org/jira/browse/CAMEL-18381 > Project: Camel > Issue Type: Improvement > Components: camel-test-infra, camel-test-infra-couchbase >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.x > > > Add support for more singleton services in test infra. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18686) camel-resume-api: remove configuration via registry
[ https://issues.apache.org/jira/browse/CAMEL-18686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18686: Fix Version/s: 4.x (was: 4.1.0) > camel-resume-api: remove configuration via registry > --- > > Key: CAMEL-18686 > URL: https://issues.apache.org/jira/browse/CAMEL-18686 > Project: Camel > Issue Type: Improvement > Components: camel-resume-api >Affects Versions: 3.19.0 >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.x > > > Remove the configuration using keys via the registry. Default to > auto-configuration on the route. This makes the implementation simpler on > Camel K and Camel Quarkus. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18858) camel-core - Filter out kamelet routes so they do not clutter the list of routes
[ https://issues.apache.org/jira/browse/CAMEL-18858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18858: Fix Version/s: 4.2.0 (was: 4.1.0) > camel-core - Filter out kamelet routes so they do not clutter the list of > routes > > > Key: CAMEL-18858 > URL: https://issues.apache.org/jira/browse/CAMEL-18858 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.2.0 > > > When using kamelets then they are implemented as a route, and therefore when > end users are using a kamelet (sink or source) then additional routes are > added to the management in JMX / camel-jbang etc. > We may want to have an option where you can turn these kamelet routes on|off > so they do not "clutter". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19013) camel-jbang - Add build command
[ https://issues.apache.org/jira/browse/CAMEL-19013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19013: Fix Version/s: 4.x (was: 4.1.0) > camel-jbang - Add build command > --- > > Key: CAMEL-19013 > URL: https://issues.apache.org/jira/browse/CAMEL-19013 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Priority: Minor > Fix For: 4.x > > > Sometimes users want to quickly try to build a fat-jar or native compilation > with camel-jbang. > We can then do export and use mvn package in the background. > This can be useful for users that are not to familiar with maven or gradle > how to do that. > It can be useful to prototype if the build would work or even allow to do > native builds. However the tricky part is that graalvm must be installed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19253) camel-jbang - Make it easier to use JDBC datasource
[ https://issues.apache.org/jira/browse/CAMEL-19253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19253: Fix Version/s: 4.2.0 (was: 4.1.0) > camel-jbang - Make it easier to use JDBC datasource > --- > > Key: CAMEL-19253 > URL: https://issues.apache.org/jira/browse/CAMEL-19253 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.2.0 > > > For example to configure a datasource in a .properties file in either quarkus > or spring-boot style. > https://github.com/apache/camel-k-examples/blob/main/generic-examples/databases/datasource.properties > And in plain camel-main style as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19241) Adding a Kafka Batch Consumer
[ https://issues.apache.org/jira/browse/CAMEL-19241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19241: Fix Version/s: 4.2.0 (was: 4.1.0) > Adding a Kafka Batch Consumer > - > > Key: CAMEL-19241 > URL: https://issues.apache.org/jira/browse/CAMEL-19241 > Project: Camel > Issue Type: New Feature > Components: camel-kafka >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19057) Be able to configure SpringJAXRSServerFactoryBean with performInvocation property
[ https://issues.apache.org/jira/browse/CAMEL-19057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19057: Fix Version/s: 4.x (was: 4.1.0) > Be able to configure SpringJAXRSServerFactoryBean with performInvocation > property > - > > Key: CAMEL-19057 > URL: https://issues.apache.org/jira/browse/CAMEL-19057 > Project: Camel > Issue Type: Improvement > Components: camel-cxfrs >Reporter: Freeman Yue Fang >Assignee: Freeman Yue Fang >Priority: Major > Fix For: 4.x > > > So we can easily define the cxfrs endpoint java code bean in spring boot > runtime -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18998) camel-ftp: FromFileToFtpSplitParallelIT tests a hanging up
[ https://issues.apache.org/jira/browse/CAMEL-18998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18998: Fix Version/s: 4.2.0 (was: 4.1.0) > camel-ftp: FromFileToFtpSplitParallelIT tests a hanging up > -- > > Key: CAMEL-18998 > URL: https://issues.apache.org/jira/browse/CAMEL-18998 > Project: Camel > Issue Type: Test >Affects Versions: 4.0-M1 >Reporter: Otavio Rodolfo Piske >Assignee: Nikita_Konovalov >Priority: Major > Labels: easy, help-wanted > Fix For: 4.2.0 > > Attachments: camel-ftp-test.log > > > Since we upgraded to surefire + failsafe M8, some of our tests have started > to hang up. > The logs from a manual execution is attached. > > [^camel-ftp-test.log] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19041) camel-jbang - Run with runtime
[ https://issues.apache.org/jira/browse/CAMEL-19041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19041: Fix Version/s: (was: 4.1.0) 4.x > camel-jbang - Run with runtime > -- > > Key: CAMEL-19041 > URL: https://issues.apache.org/jira/browse/CAMEL-19041 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.x > > > So you can do camel run foo.java --runtime=spring-boot -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19557) camel-core: ensure tests have assertions
[ https://issues.apache.org/jira/browse/CAMEL-19557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19557: Fix Version/s: 4.2.0 (was: 4.1.0) > camel-core: ensure tests have assertions > > > Key: CAMEL-19557 > URL: https://issues.apache.org/jira/browse/CAMEL-19557 > Project: Camel > Issue Type: Task > Components: camel-core, tests >Affects Versions: 4.0.0 >Reporter: Otavio Rodolfo Piske >Assignee: Nikita_Konovalov >Priority: Minor > Labels: easy, help-wanted > Fix For: 4.2.0 > > > Some tests do not have assertions and that prevents us from fully > understanding what is a test failure and what is an error. In many cases, > these are tests that were originally written with older versions of JUnit in > mind (i.e: equal or older than v4), so they lack modernization. > > We should ensure every test has an assertion. The assertion does not, > necessarily, needs to be visible (i.e.: it can be called in a separate > method). > > When asserting that a piece of code does not throw an error, we should use > JUnit's 5 > [assertDoesNotThrow|https://junit.org/junit5/docs/5.8.2/api/org.junit.jupiter.api/org/junit/jupiter/api/Assertions.html#assertDoesNotThrow(org.junit.jupiter.api.function.Executable)] > (either the linked method or one of the others with different signatures). > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19409) camel-salesforce - Can not re-subscribe to CDC channel data/ChangeEvents
[ https://issues.apache.org/jira/browse/CAMEL-19409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19409: Fix Version/s: 4.2.0 (was: 4.1.0) > camel-salesforce - Can not re-subscribe to CDC channel data/ChangeEvents > > > Key: CAMEL-19409 > URL: https://issues.apache.org/jira/browse/CAMEL-19409 > Project: Camel > Issue Type: Bug > Components: camel-salesforce >Affects Versions: 3.18.3, 3.19.0 >Reporter: Iva >Priority: Major > Fix For: 3.22.0, 4.2.0 > > Attachments: stack-with-pr.txt, stacktrace.txt > > > Hello, I have problem with connection to the salesforce channel ChangeEvents. > I am using quarkus - version 2.13.7 and camel with version 3.18.3 and when an > error occurs my application is not re-subscribing to the channel after that. > Do you know if it is problem from the camel version or do you have any idea > how I can fix it? Thank you in advance > Edit 1: You can find the stacktrace of the exception in this file > [^stacktrace.txt] > The problem seems to be fixed after a restart of the pod but it is not > relevant solution. I have seen similar issue that is said to be fixed in > version 3.14 but it looks like now I have the same problem in latest version > https://issues.apache.org/jira/browse/CAMEL-16370 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19667) camel-tracing: Context is not propagated from exchange header to OpenTelemetry Context
[
https://issues.apache.org/jira/browse/CAMEL-19667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-19667:
Fix Version/s: 4.2.0
(was: 4.1.0)
> camel-tracing: Context is not propagated from exchange header to
> OpenTelemetry Context
> --
>
> Key: CAMEL-19667
> URL: https://issues.apache.org/jira/browse/CAMEL-19667
> Project: Camel
> Issue Type: Improvement
> Components: camel-opentelemetry, camel-tracing
>Affects Versions: 3.20.5, 3.20.6, 3.21.0, 4.0-M3
>Reporter: Roman Kvasnytskyi
>Priority: Major
> Labels: bug, opentelemetry, tracing
> Fix For: 4.2.0
>
>
> I am using OpenTelemetry Agent for tracing along with
> camel-opentelemetry-starter that configures OpenTelemetryTracer for Camel
> aligned with camel-tracing.
> I see my spans for Camel inside a single trace, but after control is passed
> to the Processor process method next spans are disassociated from the trace
> and are created in the separate trace.
> The tracing context does not seem to get propagated, and the resulting spans
> end up being disassociated. For example:
> {code:java}
> from("timer:tick?period=5s)
> .process("myProcessor");
> {code}
> {code:java}
> public class MyProcessor implements Processor {
> private final HttpClient someClient = new HttpClient();
> @Override
> public void process(Exchange exchange) {
> // http client is instrumented and also produces spans
> someClient.get('/example');
> }
> }
> {code}
> This results in 2 spans. One for timer:tick & another for a client call. The
> problem is that the parent span for client calls is not set, so they appear
> as 2 distinct traces.
> My exchange headers contain traceparent header with all data which should be
> put inside the OpenTelemetry context, but they do not.
> I have come up with a workaround. The idea is trivial - get traceparent
> header if it is present in exchange, parse trace metadata from it, create a
> SpanContext object, and put it as a parent for the current OpenTelemetry
> context.
> It looks like this:
> {code:java}
> public class TraceEnrichingProcessor implements Processor {
> private final Processor delegate;
> public TraceEnrichingProcessor(Processor delegate) {
> this.delegate = delegate;
> }
> @Override
> public void process(Exchange exchange) throws Exception {
> // Get the existing traceparent header from the Exchange
> String traceparent = exchange.getIn().getHeader("traceparent",
> String.class);
> if (traceparent != null && !traceparent.isEmpty()) {
> // Extract the traceId, parentSpanId and sampleFlag
> String[] parts = traceparent.split("-");
> String traceId = parts[1];
> String parentSpanId = parts[2];
> boolean isSampled = parts[3].equals("01");
> // Create the parent SpanContext
> SpanContext parentContext = SpanContext.create(
> traceId,
> parentSpanId,
> isSampled ? TraceFlags.getSampled() : TraceFlags.getDefault(),
> TraceState.getDefault()
> );
> // Attach the parent SpanContext to the current Context
> try (Scope scope =
> Context.current().with(Span.wrap(parentContext)).makeCurrent()) {
> // Now, the current Context has the parent SpanContext
> attached,
> // and any new spans created within this scope will use it as
> their parent
>
> // Pass control to the delegate processor
> delegate.process(exchange);
> }
> } else {
> // If no traceparent header is found, just delegate without
> modifying the Context
> delegate.process(exchange);
> }
> }
> } {code}
> Inside OpenTelemetry Agent, they dropped support of Camel 3.x+, because Camel
> provides its module for tracing, and they will not help with it.
> [Link|https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/4052]
> I wonder if that can be done inside Camel to propagate context from the
> processor implicitly without manual propagation of context.
> *UPD1:* I have verified that these behaviour is consistent across Camel
> 3.20.5, 3.20.6, 3.21.0 and 4.0.0-RC1
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-19644) camel-jbang - Add command to generate SBOM report
[ https://issues.apache.org/jira/browse/CAMEL-19644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19644: Fix Version/s: 4.2.0 (was: 4.1.0) > camel-jbang - Add command to generate SBOM report > - > > Key: CAMEL-19644 > URL: https://issues.apache.org/jira/browse/CAMEL-19644 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.2.0 > > > A command to generate sbom for a given jbang project in cyclonx format -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19707) camel-aws2-s3 multipart uploads crash with zero-byte files
[
https://issues.apache.org/jira/browse/CAMEL-19707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-19707:
Fix Version/s: 4.2.0
(was: 4.1.0)
> camel-aws2-s3 multipart uploads crash with zero-byte files
> --
>
> Key: CAMEL-19707
> URL: https://issues.apache.org/jira/browse/CAMEL-19707
> Project: Camel
> Issue Type: Improvement
> Components: camel-aws2
>Affects Versions: 4.0-RC2
>Reporter: Philippe Soares
>Priority: Minor
> Fix For: 4.2.0
>
>
> When a route is configured to upload files to S3 using multipart, the upload
> fails for files with zero length with the following stack trace:
> {code:java}
> 08:58:19.315 [Camel (camel-1) thread #3 - seda://mychannel] WARN
> o.a.c.component.seda.SedaConsumer - Error processing exchange.
> Exchange[2980AEE3A04EBAE-001D]. Caused by:
> [software.amazon.awssdk.services.s3.model.S3Exception - The XML you provided
> was not well-formed or did not validate against our published schema
> (Service: S3, Status Code: 400, Request ID: JTV2BKF1Z2JXAXMM, Extended
> Request ID:
> unKlvF+b5nZtUxqdH8Lg2fcTYCswasH/WHc8rRmKnY5cGVVp8J9vbPKX8v2o09aebAjLvoNLcV0=)]
> software.amazon.awssdk.services.s3.model.S3Exception: The XML you provided
> was not well-formed or did not validate against our published schema
> (Service: S3, Status Code: 400, Request ID: JTV2BKF1Z2JXAXMM, Extended
> Request ID:
> unKlvF+b5nZtUxqdH8Lg2fcTYCswasH/WHc8rRmKnY5cGVVp8J9vbPKX8v2o09aebAjLvoNLcV0=)
> at
> software.amazon.awssdk.protocols.xml.internal.unmarshall.AwsXmlPredicatedResponseHandler.handleErrorResponse(AwsXmlPredicatedResponseHandler.java:156)
> at
> software.amazon.awssdk.protocols.xml.internal.unmarshall.AwsXmlPredicatedResponseHandler.handleResponse(AwsXmlPredicatedResponseHandler.java:108)
> at
> software.amazon.awssdk.protocols.xml.internal.unmarshall.AwsXmlPredicatedResponseHandler.handle(AwsXmlPredicatedResponseHandler.java:85)
> at
> software.amazon.awssdk.protocols.xml.internal.unmarshall.AwsXmlPredicatedResponseHandler.handle(AwsXmlPredicatedResponseHandler.java:43)
> at
> software.amazon.awssdk.awscore.client.handler.AwsSyncClientHandler$Crc32ValidationResponseHandler.handle(AwsSyncClientHandler.java:95)
> at
> software.amazon.awssdk.core.internal.handler.BaseClientHandler.lambda$successTransformationResponseHandler$7(BaseClientHandler.java:270)
> at
> software.amazon.awssdk.core.internal.http.pipeline.stages.HandleResponseStage.execute(HandleResponseStage.java:40)
> at
> software.amazon.awssdk.core.internal.http.pipeline.stages.HandleResponseStage.execute(HandleResponseStage.java:30)
> at
> software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)
> at
> software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptTimeoutTrackingStage.execute(ApiCallAttemptTimeoutTrackingStage.java:72)
> at
> software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptTimeoutTrackingStage.execute(ApiCallAttemptTimeoutTrackingStage.java:42)
> at
> software.amazon.awssdk.core.internal.http.pipeline.stages.TimeoutExceptionHandlingStage.execute(TimeoutExceptionHandlingStage.java:78)
> at
> software.amazon.awssdk.core.internal.http.pipeline.stages.TimeoutExceptionHandlingStage.execute(TimeoutExceptionHandlingStage.java:40)
> at
> software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptMetricCollectionStage.execute(ApiCallAttemptMetricCollectionStage.java:52)
> at
> software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptMetricCollectionStage.execute(ApiCallAttemptMetricCollectionStage.java:37)
> at
> software.amazon.awssdk.core.internal.http.pipeline.stages.RetryableStage.execute(RetryableStage.java:81)
> at
> software.amazon.awssdk.core.internal.http.pipeline.stages.RetryableStage.execute(RetryableStage.java:36)
> at
> software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)
> at
> software.amazon.awssdk.core.internal.http.StreamManagingStage.execute(StreamManagingStage.java:56)
> at
> software.amazon.awssdk.core.internal.http.StreamManagingStage.execute(StreamManagingStage.java:36)
> at
> software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.executeWithTimer(ApiCallTimeoutTrackingStage.java:80)
> at
> software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.execute(ApiCallTimeoutTrackingStage.java:60)
> at
> software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.execute(ApiCallTimeoutTrac
[jira] [Resolved] (CAMEL-19718) camel-util-json should allow to configure escape forward slashes or not
[
https://issues.apache.org/jira/browse/CAMEL-19718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-19718.
-
Resolution: Won't Fix
Ah lets just use jackson in this maven plugin
> camel-util-json should allow to configure escape forward slashes or not
> ---
>
> Key: CAMEL-19718
> URL: https://issues.apache.org/jira/browse/CAMEL-19718
> Project: Camel
> Issue Type: Improvement
> Components: tooling
>Reporter: Luca Burgazzoli
>Priority: Minor
> Fix For: 4.1.0
>
>
> Wile exploring
> [CAMEL-19717|https://issues.apache.org/jira/browse/CAMEL-19717], I noticed
> that camel-util-json escapes i.e. slashes:
>
> {code:json}
> "beans": {
> "$ref":
> "#\/items\/definitions\/org.apache.camel.dsl.yaml.deserializers.BeansDeserializer"
> },
> {code}
> This is not required in json-schema and would be nice to have a way to
> configure JSooner to disable such behavior.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-19717) [yaml dsl] replace jackson with camel-util-json for json schema generation
[ https://issues.apache.org/jira/browse/CAMEL-19717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19717. - Resolution: Won't Fix Ah lets just use jackson in this maven plugin > [yaml dsl] replace jackson with camel-util-json for json schema generation > -- > > Key: CAMEL-19717 > URL: https://issues.apache.org/jira/browse/CAMEL-19717 > Project: Camel > Issue Type: Improvement > Components: camel-yaml-dsl >Reporter: Luca Burgazzoli >Assignee: Luca Burgazzoli >Priority: Minor > Fix For: 4.1.0 > > > as today, the yaml dsl Json schema generation leverages Jackson, however for > consistency with json code generation in Camel, it would be nice to re-write > the schema generation on top of camel-util-json -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19757) camel-examples - Move examples to root folder
[ https://issues.apache.org/jira/browse/CAMEL-19757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19757: Fix Version/s: 4.x (was: 4.1.0) > camel-examples - Move examples to root folder > - > > Key: CAMEL-19757 > URL: https://issues.apache.org/jira/browse/CAMEL-19757 > Project: Camel > Issue Type: Task > Components: examples >Reporter: Claus Ibsen >Priority: Minor > Labels: help-wanted > Fix For: 4.x > > > To make this like we have for camel-spring-boot-examples, and this makes it > easy to do full test by just run from root: mvn clean install > It also allows to build a table that lists all the examples in the readme > file. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19907) Introduce the ability to use the old Micrometer meter names or follow the new Micrometer naming conventions
[ https://issues.apache.org/jira/browse/CAMEL-19907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19907: Fix Version/s: 3.22.0 > Introduce the ability to use the old Micrometer meter names or follow the new > Micrometer naming conventions > --- > > Key: CAMEL-19907 > URL: https://issues.apache.org/jira/browse/CAMEL-19907 > Project: Camel > Issue Type: Improvement >Affects Versions: 3.21.0 >Reporter: Andrea Cosentino >Priority: Major > Fix For: 3.21.1, 3.22.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19909) camel-catalog: model catalog refers to not-existing DescriptionDefinition javaType
[ https://issues.apache.org/jira/browse/CAMEL-19909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768247#comment-17768247 ] Claus Ibsen commented on CAMEL-19909: - It affects the entire yaml schema, but its potentially a candidate for backport to 4.0.2 > camel-catalog: model catalog refers to not-existing DescriptionDefinition > javaType > -- > > Key: CAMEL-19909 > URL: https://issues.apache.org/jira/browse/CAMEL-19909 > Project: Camel > Issue Type: Task > Components: camel-catalog >Reporter: Tomohisa Igarashi >Assignee: Tomohisa Igarashi >Priority: Minor > Fix For: 4.1.0 > > > from.json model catalog says "description" is of javaType > "org.apache.camel.model.DescriptionDefinition" but the class doesn't exist. > It's just a String. > https://github.com/apache/camel/blob/main/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/models/from.json#L17 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19908) camel-quarkus-azure-servicebus - Fix typo in docs
[
https://issues.apache.org/jira/browse/CAMEL-19908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-19908.
-
Resolution: Fixed
> camel-quarkus-azure-servicebus - Fix typo in docs
> -
>
> Key: CAMEL-19908
> URL: https://issues.apache.org/jira/browse/CAMEL-19908
> Project: Camel
> Issue Type: Task
> Components: camel-azure
>Reporter: Lucia Drozdová
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.0.2, 4.1.0
>
>
> Please, there is a typo in the first sentence of AZURE SERVICEBUS docs in
> camel quarkus:
> {code:java}
> Send and receive messages to/from Azure Event Bus. {code}
> Can it be please changed to Azure Service Bus?
> Thank you.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-19908) camel-quarkus-azure-servicebus - Fix typo in docs
[
https://issues.apache.org/jira/browse/CAMEL-19908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-19908:
---
Assignee: Claus Ibsen
> camel-quarkus-azure-servicebus - Fix typo in docs
> -
>
> Key: CAMEL-19908
> URL: https://issues.apache.org/jira/browse/CAMEL-19908
> Project: Camel
> Issue Type: Task
> Components: camel-azure
>Reporter: Lucia Drozdová
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.0.2, 4.1.0
>
>
> Please, there is a typo in the first sentence of AZURE SERVICEBUS docs in
> camel quarkus:
> {code:java}
> Send and receive messages to/from Azure Event Bus. {code}
> Can it be please changed to Azure Service Bus?
> Thank you.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-19908) camel-quarkus-azure-servicebus - Fix typo in docs
[
https://issues.apache.org/jira/browse/CAMEL-19908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-19908:
Fix Version/s: 4.0.2
> camel-quarkus-azure-servicebus - Fix typo in docs
> -
>
> Key: CAMEL-19908
> URL: https://issues.apache.org/jira/browse/CAMEL-19908
> Project: Camel
> Issue Type: Task
> Components: camel-azure
>Reporter: Lucia Drozdová
>Priority: Minor
> Fix For: 4.1.0, 4.0.2
>
>
> Please, there is a typo in the first sentence of AZURE SERVICEBUS docs in
> camel quarkus:
> {code:java}
> Send and receive messages to/from Azure Event Bus. {code}
> Can it be please changed to Azure Service Bus?
> Thank you.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-19908) camel-quarkus-azure-servicebus - Fix typo in docs
[
https://issues.apache.org/jira/browse/CAMEL-19908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-19908:
Fix Version/s: 4.1.0
> camel-quarkus-azure-servicebus - Fix typo in docs
> -
>
> Key: CAMEL-19908
> URL: https://issues.apache.org/jira/browse/CAMEL-19908
> Project: Camel
> Issue Type: Task
> Components: camel-azure
>Reporter: Lucia Drozdová
>Priority: Minor
> Fix For: 4.1.0
>
>
> Please, there is a typo in the first sentence of AZURE SERVICEBUS docs in
> camel quarkus:
> {code:java}
> Send and receive messages to/from Azure Event Bus. {code}
> Can it be please changed to Azure Service Bus?
> Thank you.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-19906) Camel-Jbang: No need to have specific application properties exports for Secret Refresh features
[ https://issues.apache.org/jira/browse/CAMEL-19906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-19906. -- Resolution: Fixed > Camel-Jbang: No need to have specific application properties exports for > Secret Refresh features > > > Key: CAMEL-19906 > URL: https://issues.apache.org/jira/browse/CAMEL-19906 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.1.0 > > > If you have an application.properties file containing all the needed bits, > they will be exported directly, so some code could be removed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19906) Camel-Jbang: No need to have specific application properties exports for Secret Refresh features
[ https://issues.apache.org/jira/browse/CAMEL-19906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19906: Component/s: camel-jbang > Camel-Jbang: No need to have specific application properties exports for > Secret Refresh features > > > Key: CAMEL-19906 > URL: https://issues.apache.org/jira/browse/CAMEL-19906 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.1.0 > > > If you have an application.properties file containing all the needed bits, > they will be exported directly, so some code could be removed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19877) camel-file - Add option to accept hidden folders
[ https://issues.apache.org/jira/browse/CAMEL-19877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19877: Fix Version/s: 4.1.0 (was: 4.x) > camel-file - Add option to accept hidden folders > > > Key: CAMEL-19877 > URL: https://issues.apache.org/jira/browse/CAMEL-19877 > Project: Camel > Issue Type: New Feature > Components: camel-file >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.1.0 > > > See CAMEL-19716 > includeHiddenDir=true|false -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19909) camel-catalog: model catalog refers to not-existing DescriptionDefinition javaType
[ https://issues.apache.org/jira/browse/CAMEL-19909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19909: Component/s: camel-catalog (was: Catalog) > camel-catalog: model catalog refers to not-existing DescriptionDefinition > javaType > -- > > Key: CAMEL-19909 > URL: https://issues.apache.org/jira/browse/CAMEL-19909 > Project: Camel > Issue Type: Task > Components: camel-catalog >Reporter: Tomohisa Igarashi >Assignee: Tomohisa Igarashi >Priority: Minor > Fix For: 4.1.0 > > > from.json model catalog says "description" is of javaType > "org.apache.camel.model.DescriptionDefinition" but the class doesn't exist. > It's just a String. > https://github.com/apache/camel/blob/main/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/models/from.json#L17 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19909) camel-catalog: model catalog refers to not-existing DescriptionDefinition javaType
[ https://issues.apache.org/jira/browse/CAMEL-19909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19909: Fix Version/s: 4.1.0 > camel-catalog: model catalog refers to not-existing DescriptionDefinition > javaType > -- > > Key: CAMEL-19909 > URL: https://issues.apache.org/jira/browse/CAMEL-19909 > Project: Camel > Issue Type: Task > Components: Catalog >Reporter: Tomohisa Igarashi >Assignee: Tomohisa Igarashi >Priority: Minor > Fix For: 4.1.0 > > > from.json model catalog says "description" is of javaType > "org.apache.camel.model.DescriptionDefinition" but the class doesn't exist. > It's just a String. > https://github.com/apache/camel/blob/main/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/models/from.json#L17 -- This message was sent by Atlassian Jira (v8.20.10#820010)
