[jira] [Commented] (CAMEL-20668) camel-sftp - Issue with autoCreateKnownHostsFile
[
https://issues.apache.org/jira/browse/CAMEL-20668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17836884#comment-17836884
]
Saravanakumar Selvaraj commented on CAMEL-20668:
After further investigation, I realized that the issue was with my
configuration. Setting the {{serverHostKeys}} option to {{ssh-rsa}} resolved
the problem, and {{camel-sftp}} indeed generates the knownHosts file as
expected. Apologies for any confusion caused, and thank you for your support!
> camel-sftp - Issue with autoCreateKnownHostsFile
> -
>
> Key: CAMEL-20668
> URL: https://issues.apache.org/jira/browse/CAMEL-20668
> Project: Camel
> Issue Type: Bug
> Components: camel-sftp
>Affects Versions: 4.4.1
>Reporter: Saravanakumar Selvaraj
>Priority: Minor
>
> I'm encountering a problem with {{camel-sftp}} where the
> {{autoCreateKnownHostsFile}} option doesn't seem to be functioning as
> expected. According to the documentation, setting
> {{autoCreateKnownHostsFile}} to {{true}} should automatically create the
> known hosts file if it doesn't exist. However, in my testing, the file is not
> being created as expected.
> *Steps to Reproduce:*
> # Configure {{camel-sftp}} route with {{autoCreateKnownHostsFile}} set to
> {{{}true{}}}.
> # Start the application and establish an SFTP connection.
> # Check if the known hosts file is created in the specified location.
> *Expected Behavior:* The {{autoCreateKnownHostsFile}} option should create
> the known hosts file if it doesn't exist, ensuring that host key verification
> works as intended.
> *Actual Behavior:* The known hosts file is not created automatically, leading
> to host key verification issues.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20668) camel-sftp - Issue with autoCreateKnownHostsFile
[
https://issues.apache.org/jira/browse/CAMEL-20668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saravanakumar Selvaraj resolved CAMEL-20668.
Resolution: Not A Bug
> camel-sftp - Issue with autoCreateKnownHostsFile
> -
>
> Key: CAMEL-20668
> URL: https://issues.apache.org/jira/browse/CAMEL-20668
> Project: Camel
> Issue Type: Bug
> Components: camel-sftp
>Affects Versions: 4.4.1
>Reporter: Saravanakumar Selvaraj
>Priority: Minor
>
> I'm encountering a problem with {{camel-sftp}} where the
> {{autoCreateKnownHostsFile}} option doesn't seem to be functioning as
> expected. According to the documentation, setting
> {{autoCreateKnownHostsFile}} to {{true}} should automatically create the
> known hosts file if it doesn't exist. However, in my testing, the file is not
> being created as expected.
> *Steps to Reproduce:*
> # Configure {{camel-sftp}} route with {{autoCreateKnownHostsFile}} set to
> {{{}true{}}}.
> # Start the application and establish an SFTP connection.
> # Check if the known hosts file is created in the specified location.
> *Expected Behavior:* The {{autoCreateKnownHostsFile}} option should create
> the known hosts file if it doesn't exist, ensuring that host key verification
> works as intended.
> *Actual Behavior:* The known hosts file is not created automatically, leading
> to host key verification issues.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20666) RouteDefinition DSL Consistency for XML vs YAML DSL
[ https://issues.apache.org/jira/browse/CAMEL-20666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17836818#comment-17836818 ] Marat Gubaidullin commented on CAMEL-20666: --- It looks like it is related to this one https://issues.apache.org/jira/browse/CAMEL-20667 In *YAML* DSL *RouteDefinition* *errorHandler* is *ErrorHandlerFactory* In *JAVA* DSL *RouteDefinition* *errorHandler* is *ErrorHandlerDefinition* If we sync to use *ErrorHandlerDefinition* in both then we do not need *ErrorHandlerFactory* > RouteDefinition DSL Consistency for XML vs YAML DSL > --- > > Key: CAMEL-20666 > URL: https://issues.apache.org/jira/browse/CAMEL-20666 > Project: Camel > Issue Type: Improvement > Components: camel-catalog, camel-yaml-dsl >Affects Versions: 4.5.0 >Reporter: Marat Gubaidullin >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.6.0 > > Attachments: Screenshot 2024-04-10 at 4.35.49 PM.png, Screenshot > 2024-04-10 at 4.36.23 PM.png > > > org.apache.camel.model.RouteDefinition in YAML DSL has *errorHandler* > !Screenshot 2024-04-10 at 4.35.49 PM.png! > in camel-catalog there is no *errorHandler* property > !Screenshot 2024-04-10 at 4.36.23 PM.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20672) Camel-jbang does not use application.properties when run with --source-dir
Marat Gubaidullin created CAMEL-20672:
-
Summary: Camel-jbang does not use application.properties when run
with --source-dir
Key: CAMEL-20672
URL: https://issues.apache.org/jira/browse/CAMEL-20672
Project: Camel
Issue Type: Bug
Components: camel-jbang
Affects Versions: 4.5.0
Reporter: Marat Gubaidullin
When run with {{--source-dir}} option camel-jbang does not use
{{application.properties}} from {{--source-dir}} folder,
so it is not possible to set any properties.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20664) camel-mapstruct - MapStruct mappers not found in Spring Boot
[
https://issues.apache.org/jira/browse/CAMEL-20664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20664:
Fix Version/s: 4.4.0
(was: 4.6.0)
> camel-mapstruct - MapStruct mappers not found in Spring Boot
>
>
> Key: CAMEL-20664
> URL: https://issues.apache.org/jira/browse/CAMEL-20664
> Project: Camel
> Issue Type: Bug
> Components: camel-mapstruct
>Affects Versions: 4.0.0
> Environment: $ java -version
> openjdk version "17.0.7" 2023-04-18
> OpenJDK Runtime Environment Temurin-17.0.7+7 (build 17.0.7+7)
> OpenJDK 64-Bit Server VM Temurin-17.0.7+7 (build 17.0.7+7, mixed mode,
> sharing)
>Reporter: Josh Reagan
>Priority: Minor
> Fix For: 4.4.0
>
> Attachments: camel-mapstruct-demo.zip
>
>
> The `DefaultMapStructFinder` is unable to locate the `Mapper` classes when
> running in Spring Boot. Seems to throw an exception calling
> `PluginHelper.getPackageScanClassResolver(ecc).findByFilter(f ->
> f.getName().endsWith("Mapper"), names);` inside the `doInit()` method.
> You can work around this by creating your own `MapStructFinder`, extending
> `DefaultMapStructFinder`, overriding the `doInit()` function, and calling
> `discoverMappings(...)` with each of your `Mapper` classes. That way it
> doesn't try to scan the classpath to find the `Mapper` classes automatically.
> I've attached a working example to illustrate.
> *Note: It has no issue locating them when running `mvn spring-boot:run`. Only
> when running from the packaged uber jar with `java -jar ...`.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20664) camel-mapstruct - MapStruct mappers not found in Spring Boot
[
https://issues.apache.org/jira/browse/CAMEL-20664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20664.
-
Resolution: Information Provided
> camel-mapstruct - MapStruct mappers not found in Spring Boot
>
>
> Key: CAMEL-20664
> URL: https://issues.apache.org/jira/browse/CAMEL-20664
> Project: Camel
> Issue Type: Bug
> Components: camel-mapstruct
>Affects Versions: 4.0.0
> Environment: $ java -version
> openjdk version "17.0.7" 2023-04-18
> OpenJDK Runtime Environment Temurin-17.0.7+7 (build 17.0.7+7)
> OpenJDK 64-Bit Server VM Temurin-17.0.7+7 (build 17.0.7+7, mixed mode,
> sharing)
>Reporter: Josh Reagan
>Priority: Minor
> Fix For: 4.4.0
>
> Attachments: camel-mapstruct-demo.zip
>
>
> The `DefaultMapStructFinder` is unable to locate the `Mapper` classes when
> running in Spring Boot. Seems to throw an exception calling
> `PluginHelper.getPackageScanClassResolver(ecc).findByFilter(f ->
> f.getName().endsWith("Mapper"), names);` inside the `doInit()` method.
> You can work around this by creating your own `MapStructFinder`, extending
> `DefaultMapStructFinder`, overriding the `doInit()` function, and calling
> `discoverMappings(...)` with each of your `Mapper` classes. That way it
> doesn't try to scan the classpath to find the `Mapper` classes automatically.
> I've attached a working example to illustrate.
> *Note: It has no issue locating them when running `mvn spring-boot:run`. Only
> when running from the packaged uber jar with `java -jar ...`.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20664) camel-mapstruct - MapStruct mappers not found in Spring Boot
[
https://issues.apache.org/jira/browse/CAMEL-20664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17836810#comment-17836810
]
Claus Ibsen commented on CAMEL-20664:
-
Okay removing that custom resolver so its plain OOTB then it works for
4.4.1, 4.5.0, 4.6-SNAPSHOT
And it fails for 4.0.x
You can upgrade to Camel 4.4.x
> camel-mapstruct - MapStruct mappers not found in Spring Boot
>
>
> Key: CAMEL-20664
> URL: https://issues.apache.org/jira/browse/CAMEL-20664
> Project: Camel
> Issue Type: Bug
> Components: camel-mapstruct
>Affects Versions: 4.0.0
> Environment: $ java -version
> openjdk version "17.0.7" 2023-04-18
> OpenJDK Runtime Environment Temurin-17.0.7+7 (build 17.0.7+7)
> OpenJDK 64-Bit Server VM Temurin-17.0.7+7 (build 17.0.7+7, mixed mode,
> sharing)
>Reporter: Josh Reagan
>Priority: Minor
> Fix For: 4.6.0
>
> Attachments: camel-mapstruct-demo.zip
>
>
> The `DefaultMapStructFinder` is unable to locate the `Mapper` classes when
> running in Spring Boot. Seems to throw an exception calling
> `PluginHelper.getPackageScanClassResolver(ecc).findByFilter(f ->
> f.getName().endsWith("Mapper"), names);` inside the `doInit()` method.
> You can work around this by creating your own `MapStructFinder`, extending
> `DefaultMapStructFinder`, overriding the `doInit()` function, and calling
> `discoverMappings(...)` with each of your `Mapper` classes. That way it
> doesn't try to scan the classpath to find the `Mapper` classes automatically.
> I've attached a working example to illustrate.
> *Note: It has no issue locating them when running `mvn spring-boot:run`. Only
> when running from the packaged uber jar with `java -jar ...`.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20664) camel-mapstruct - MapStruct mappers not found in Spring Boot
[
https://issues.apache.org/jira/browse/CAMEL-20664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17836807#comment-17836807
]
Claus Ibsen commented on CAMEL-20664:
-
What is your example supposed to output in the logs to make it work. I see this
12:47:23.937 [Camel (camel-1) thread #1 - timer://kickstartmyroute] INFO
c.redhat.examples.CamelConfiguration - Processed order:
[{"id":null,"customer":"1","item":"1","description":null,"quantity":4}]
> camel-mapstruct - MapStruct mappers not found in Spring Boot
>
>
> Key: CAMEL-20664
> URL: https://issues.apache.org/jira/browse/CAMEL-20664
> Project: Camel
> Issue Type: Bug
> Components: camel-mapstruct
>Affects Versions: 4.0.0
> Environment: $ java -version
> openjdk version "17.0.7" 2023-04-18
> OpenJDK Runtime Environment Temurin-17.0.7+7 (build 17.0.7+7)
> OpenJDK 64-Bit Server VM Temurin-17.0.7+7 (build 17.0.7+7, mixed mode,
> sharing)
>Reporter: Josh Reagan
>Priority: Minor
> Fix For: 4.6.0
>
> Attachments: camel-mapstruct-demo.zip
>
>
> The `DefaultMapStructFinder` is unable to locate the `Mapper` classes when
> running in Spring Boot. Seems to throw an exception calling
> `PluginHelper.getPackageScanClassResolver(ecc).findByFilter(f ->
> f.getName().endsWith("Mapper"), names);` inside the `doInit()` method.
> You can work around this by creating your own `MapStructFinder`, extending
> `DefaultMapStructFinder`, overriding the `doInit()` function, and calling
> `discoverMappings(...)` with each of your `Mapper` classes. That way it
> doesn't try to scan the classpath to find the `Mapper` classes automatically.
> I've attached a working example to illustrate.
> *Note: It has no issue locating them when running `mvn spring-boot:run`. Only
> when running from the packaged uber jar with `java -jar ...`.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-20664) camel-mapstruct - MapStruct mappers not found in Spring Boot
[
https://issues.apache.org/jira/browse/CAMEL-20664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17836806#comment-17836806
]
Claus Ibsen edited comment on CAMEL-20664 at 4/13/24 10:49 AM:
---
Can you try with a newer camel version.
This works for me for 4.6-SNAPSHOT, 4.5.0, and 4.4.1 releases of Apache Camel
{code}
~/Downloads/camel-mapstruct-demo ❯ java -jar
target/order-processor-1.0.0-SNAPSHOT.jar
. ___ _ _
/\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
\\/ ___)| |_)| | | | | || (_| | ) ) ) )
' || .__|_| |_|_| |_\__, | / / / /
=|_|==|___/=/_/_/_/
:: Spring Boot ::(v3.2.4)
12:47:20.773 [main] INFO com.redhat.examples.Application - Starting
Application using Java 17.0.5 with PID 20269
(/Users/davsclaus/Downloads/camel-mapstruct-demo/target/order-processor-1.0.0-SNAPSHOT.jar
started by davsclaus in /Users/davsclaus/Downloads/camel-mapstruct-demo)
12:47:20.775 [main] INFO com.redhat.examples.Application - No active profile
set, falling back to 1 default profile: "default"
12:47:21.691 [main] WARN io.undertow.websockets.jsr - UT026010: Buffer pool
was not set on WebSocketDeploymentInfo, the default pool will be used
12:47:21.704 [main] INFO io.undertow.servlet - Initializing Spring embedded
WebApplicationContext
12:47:21.704 [main] INFO o.s.b.w.s.c.ServletWebServerApplicationContext - Root
WebApplicationContext: initialization completed in 877 ms
12:47:22.304 [main] INFO o.s.b.a.e.web.EndpointLinksResolver - Exposing 3
endpoint(s) beneath base path '/actuator'
12:47:22.374 [main] INFO io.undertow - starting server: Undertow - 2.3.12.Final
12:47:22.381 [main] INFO org.xnio - XNIO version 3.8.8.Final
12:47:22.387 [main] INFO org.xnio.nio - XNIO NIO Implementation Version
3.8.8.Final
12:47:22.434 [main] INFO org.jboss.threads - JBoss Threads version 3.5.0.Final
12:47:22.463 [main] INFO o.s.b.w.e.undertow.UndertowWebServer - Undertow
started on port 8080 (http)
12:47:22.725 [main] INFO o.a.c.i.engine.AbstractCamelContext - Apache Camel
4.6.0-SNAPSHOT (camel-processor) is starting
12:47:22.727 [main] WARN o.a.c.c.mapstruct.MapstructComponent - Cannot find
MapStruct Mapper classes because mapperPackageName has not been configured
12:47:22.853 [main] INFO o.a.c.i.engine.AbstractCamelContext - Routes startup
(total:1)
12:47:22.853 [main] INFO o.a.c.i.engine.AbstractCamelContext - Started
route1 (timer://kickstartmyroute)
12:47:22.853 [main] INFO o.a.c.i.engine.AbstractCamelContext - Apache Camel
4.6.0-SNAPSHOT (camel-processor) started in 127ms (build:0ms init:0ms
start:127ms)
12:47:22.855 [main] INFO com.redhat.examples.Application - Started Application
in 2.365 seconds (process running for 2.717)
12:47:23.878 [Camel (camel-1) thread #1 - timer://kickstartmyroute] INFO
c.redhat.examples.CamelConfiguration - Raw order:
[114]
12:47:23.882 [Camel (camel-1) thread #1 - timer://kickstartmyroute] INFO
o.a.c.converter.jaxp.StaxConverter - Created XMLInputFactory:
com.sun.xml.internal.stream.XMLInputFactoryImpl@55ae2ff4. DOMSource/DOMResult
may have issues with com.sun.xml.internal.stream.XMLInputFactoryImpl@55ae2ff4.
We suggest using Woodstox.
12:47:23.937 [Camel (camel-1) thread #1 - timer://kickstartmyroute] INFO
c.redhat.examples.CamelConfiguration - Processed order:
[{"id":null,"customer":"1","item":"1","description":null,"quantity":4}]
^C12:47:26.606 [SpringApplicationShutdownHook] INFO io.undertow - stopping
server: Undertow - 2.3.12.Final
12:47:26.613 [SpringApplicationShutdownHook] INFO
o.a.c.i.engine.AbstractCamelContext - Apache Camel 4.6.0-SNAPSHOT
(camel-processor) is shutting down (timeout:45s)
12:47:26.619 [SpringApplicationShutdownHook] INFO
o.a.c.i.engine.AbstractCamelContext - Routes stopped (total:1)
12:47:26.620 [SpringApplicationShutdownHook] INFO
o.a.c.i.engine.AbstractCamelContext - Stopped route1
(timer://kickstartmyroute)
12:47:26.622 [SpringApplicationShutdownHook] INFO
o.a.c.i.engine.AbstractCamelContext - Apache Camel 4.6.0-SNAPSHOT
(camel-processor) shutdown in 8ms (uptime:3s)
{code}
was (Author: davsclaus):
Can you try with a newer camel version.
This works for me for 4.6
{code}
~/Downloads/camel-mapstruct-demo ❯ java -jar
target/order-processor-1.0.0-SNAPSHOT.jar
. ___ _ _
/\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
\\/ ___)| |_)| | | | | || (_| | ) ) ) )
' || .__|_| |_|_| |_\__, | / / / /
=|_|==|___/=/_/_/_/
:: Spring Boot ::(v3.2.4)
12:47:20.773 [main] INFO com.redhat.examples.Application - Starting
Application using Java 17.0.5 with PID 20269
(/Users/davsclaus/Downloads/camel-mapstruct-demo/target/order-processor-1.0.0-SNAPSHOT.jar
started by davsclaus in /Users/davsclaus
[jira] [Commented] (CAMEL-20664) camel-mapstruct - MapStruct mappers not found in Spring Boot
[
https://issues.apache.org/jira/browse/CAMEL-20664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17836806#comment-17836806
]
Claus Ibsen commented on CAMEL-20664:
-
Can you try with a newer camel version.
This works for me for 4.6
{code}
~/Downloads/camel-mapstruct-demo ❯ java -jar
target/order-processor-1.0.0-SNAPSHOT.jar
. ___ _ _
/\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
\\/ ___)| |_)| | | | | || (_| | ) ) ) )
' || .__|_| |_|_| |_\__, | / / / /
=|_|==|___/=/_/_/_/
:: Spring Boot ::(v3.2.4)
12:47:20.773 [main] INFO com.redhat.examples.Application - Starting
Application using Java 17.0.5 with PID 20269
(/Users/davsclaus/Downloads/camel-mapstruct-demo/target/order-processor-1.0.0-SNAPSHOT.jar
started by davsclaus in /Users/davsclaus/Downloads/camel-mapstruct-demo)
12:47:20.775 [main] INFO com.redhat.examples.Application - No active profile
set, falling back to 1 default profile: "default"
12:47:21.691 [main] WARN io.undertow.websockets.jsr - UT026010: Buffer pool
was not set on WebSocketDeploymentInfo, the default pool will be used
12:47:21.704 [main] INFO io.undertow.servlet - Initializing Spring embedded
WebApplicationContext
12:47:21.704 [main] INFO o.s.b.w.s.c.ServletWebServerApplicationContext - Root
WebApplicationContext: initialization completed in 877 ms
12:47:22.304 [main] INFO o.s.b.a.e.web.EndpointLinksResolver - Exposing 3
endpoint(s) beneath base path '/actuator'
12:47:22.374 [main] INFO io.undertow - starting server: Undertow - 2.3.12.Final
12:47:22.381 [main] INFO org.xnio - XNIO version 3.8.8.Final
12:47:22.387 [main] INFO org.xnio.nio - XNIO NIO Implementation Version
3.8.8.Final
12:47:22.434 [main] INFO org.jboss.threads - JBoss Threads version 3.5.0.Final
12:47:22.463 [main] INFO o.s.b.w.e.undertow.UndertowWebServer - Undertow
started on port 8080 (http)
12:47:22.725 [main] INFO o.a.c.i.engine.AbstractCamelContext - Apache Camel
4.6.0-SNAPSHOT (camel-processor) is starting
12:47:22.727 [main] WARN o.a.c.c.mapstruct.MapstructComponent - Cannot find
MapStruct Mapper classes because mapperPackageName has not been configured
12:47:22.853 [main] INFO o.a.c.i.engine.AbstractCamelContext - Routes startup
(total:1)
12:47:22.853 [main] INFO o.a.c.i.engine.AbstractCamelContext - Started
route1 (timer://kickstartmyroute)
12:47:22.853 [main] INFO o.a.c.i.engine.AbstractCamelContext - Apache Camel
4.6.0-SNAPSHOT (camel-processor) started in 127ms (build:0ms init:0ms
start:127ms)
12:47:22.855 [main] INFO com.redhat.examples.Application - Started Application
in 2.365 seconds (process running for 2.717)
12:47:23.878 [Camel (camel-1) thread #1 - timer://kickstartmyroute] INFO
c.redhat.examples.CamelConfiguration - Raw order:
[114]
12:47:23.882 [Camel (camel-1) thread #1 - timer://kickstartmyroute] INFO
o.a.c.converter.jaxp.StaxConverter - Created XMLInputFactory:
com.sun.xml.internal.stream.XMLInputFactoryImpl@55ae2ff4. DOMSource/DOMResult
may have issues with com.sun.xml.internal.stream.XMLInputFactoryImpl@55ae2ff4.
We suggest using Woodstox.
12:47:23.937 [Camel (camel-1) thread #1 - timer://kickstartmyroute] INFO
c.redhat.examples.CamelConfiguration - Processed order:
[{"id":null,"customer":"1","item":"1","description":null,"quantity":4}]
^C12:47:26.606 [SpringApplicationShutdownHook] INFO io.undertow - stopping
server: Undertow - 2.3.12.Final
12:47:26.613 [SpringApplicationShutdownHook] INFO
o.a.c.i.engine.AbstractCamelContext - Apache Camel 4.6.0-SNAPSHOT
(camel-processor) is shutting down (timeout:45s)
12:47:26.619 [SpringApplicationShutdownHook] INFO
o.a.c.i.engine.AbstractCamelContext - Routes stopped (total:1)
12:47:26.620 [SpringApplicationShutdownHook] INFO
o.a.c.i.engine.AbstractCamelContext - Stopped route1
(timer://kickstartmyroute)
12:47:26.622 [SpringApplicationShutdownHook] INFO
o.a.c.i.engine.AbstractCamelContext - Apache Camel 4.6.0-SNAPSHOT
(camel-processor) shutdown in 8ms (uptime:3s)
{code}
> camel-mapstruct - MapStruct mappers not found in Spring Boot
>
>
> Key: CAMEL-20664
> URL: https://issues.apache.org/jira/browse/CAMEL-20664
> Project: Camel
> Issue Type: Bug
> Components: camel-mapstruct
>Affects Versions: 4.0.0
> Environment: $ java -version
> openjdk version "17.0.7" 2023-04-18
> OpenJDK Runtime Environment Temurin-17.0.7+7 (build 17.0.7+7)
> OpenJDK 64-Bit Server VM Temurin-17.0.7+7 (build 17.0.7+7, mixed mode,
> sharing)
>Reporter: Josh Reagan
>Priority: Minor
> Fix For: 4.6.0
>
> Attachments: camel-mapstruct-demo.zip
>
>
> The `DefaultMapStructFinder` is unable to locate the `Mapper` classes when
> running in Spring Boo
[jira] [Resolved] (CAMEL-20665) YAML DSL Inconsistency - StreamCaching vs streamCache
[ https://issues.apache.org/jira/browse/CAMEL-20665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20665. - Resolution: Fixed > YAML DSL Inconsistency - StreamCaching vs streamCache > - > > Key: CAMEL-20665 > URL: https://issues.apache.org/jira/browse/CAMEL-20665 > Project: Camel > Issue Type: Improvement > Components: camel-yaml-dsl >Affects Versions: 4.5.0 >Reporter: Marat Gubaidullin >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.6.0 > > > org.apache.camel.model.RouteDefinition has `streamCache` property in > camel-catalog > [route.json|https://github.com/apache/camel/blob/afc1eb789c7c0cb3488f8610afe2aa477b366500/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/models/route.json#L22] > and `streamCaching` in YAML DSL > [camelYamlDsl.json|https://github.com/apache/camel/blob/afc1eb789c7c0cb3488f8610afe2aa477b366500/dsl/camel-yaml-dsl/camel-yaml-dsl/src/generated/resources/schema/camelYamlDsl.json#L5246C12-L5246C25] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20667) YAML DSL Consistency question - ErrorHandlerDefinition vs ErrorHandlerFactory
[ https://issues.apache.org/jira/browse/CAMEL-20667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-20667: --- Assignee: Claus Ibsen > YAML DSL Consistency question - ErrorHandlerDefinition vs ErrorHandlerFactory > - > > Key: CAMEL-20667 > URL: https://issues.apache.org/jira/browse/CAMEL-20667 > Project: Camel > Issue Type: Improvement > Components: camel-yaml-dsl >Affects Versions: 4.5.0 >Reporter: Marat Gubaidullin >Assignee: Claus Ibsen >Priority: Minor > > We have > [org.apache.camel.model.ErrorHandlerDefinition|https://github.com/apache/camel/blob/afc1eb789c7c0cb3488f8610afe2aa477b366500/dsl/camel-yaml-dsl/camel-yaml-dsl/src/generated/resources/schema/camelYamlDsl.json#L1461] > and > [org.apache.camel.ErrorHandlerFactory|https://github.com/apache/camel/blob/afc1eb789c7c0cb3488f8610afe2aa477b366500/dsl/camel-yaml-dsl/camel-yaml-dsl/src/generated/resources/schema/camelYamlDsl.json#L210C8-L210C44] > in camelYamlDsl.json > These elements have same properties and used to define error handler. > What is the goal to have similar classes with different names? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20667) YAML DSL Consistency question - ErrorHandlerDefinition vs ErrorHandlerFactory
[ https://issues.apache.org/jira/browse/CAMEL-20667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20667. - Resolution: Information Provided > YAML DSL Consistency question - ErrorHandlerDefinition vs ErrorHandlerFactory > - > > Key: CAMEL-20667 > URL: https://issues.apache.org/jira/browse/CAMEL-20667 > Project: Camel > Issue Type: Improvement > Components: camel-yaml-dsl >Affects Versions: 4.5.0 >Reporter: Marat Gubaidullin >Priority: Minor > > We have > [org.apache.camel.model.ErrorHandlerDefinition|https://github.com/apache/camel/blob/afc1eb789c7c0cb3488f8610afe2aa477b366500/dsl/camel-yaml-dsl/camel-yaml-dsl/src/generated/resources/schema/camelYamlDsl.json#L1461] > and > [org.apache.camel.ErrorHandlerFactory|https://github.com/apache/camel/blob/afc1eb789c7c0cb3488f8610afe2aa477b366500/dsl/camel-yaml-dsl/camel-yaml-dsl/src/generated/resources/schema/camelYamlDsl.json#L210C8-L210C44] > in camelYamlDsl.json > These elements have same properties and used to define error handler. > What is the goal to have similar classes with different names? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20666) RouteDefinition DSL Consistency for XML vs YAML DSL
[ https://issues.apache.org/jira/browse/CAMEL-20666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20666. - Resolution: Fixed > RouteDefinition DSL Consistency for XML vs YAML DSL > --- > > Key: CAMEL-20666 > URL: https://issues.apache.org/jira/browse/CAMEL-20666 > Project: Camel > Issue Type: Improvement > Components: camel-catalog, camel-yaml-dsl >Affects Versions: 4.5.0 >Reporter: Marat Gubaidullin >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.6.0 > > Attachments: Screenshot 2024-04-10 at 4.35.49 PM.png, Screenshot > 2024-04-10 at 4.36.23 PM.png > > > org.apache.camel.model.RouteDefinition in YAML DSL has *errorHandler* > !Screenshot 2024-04-10 at 4.35.49 PM.png! > in camel-catalog there is no *errorHandler* property > !Screenshot 2024-04-10 at 4.36.23 PM.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20667) YAML DSL Consistency question - ErrorHandlerDefinition vs ErrorHandlerFactory
[ https://issues.apache.org/jira/browse/CAMEL-20667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20667: Summary: YAML DSL Consistency question - ErrorHandlerDefinition vs ErrorHandlerFactory (was: YAML DSL Consistency question) > YAML DSL Consistency question - ErrorHandlerDefinition vs ErrorHandlerFactory > - > > Key: CAMEL-20667 > URL: https://issues.apache.org/jira/browse/CAMEL-20667 > Project: Camel > Issue Type: Improvement > Components: camel-yaml-dsl >Affects Versions: 4.5.0 >Reporter: Marat Gubaidullin >Priority: Minor > > We have > [org.apache.camel.model.ErrorHandlerDefinition|https://github.com/apache/camel/blob/afc1eb789c7c0cb3488f8610afe2aa477b366500/dsl/camel-yaml-dsl/camel-yaml-dsl/src/generated/resources/schema/camelYamlDsl.json#L1461] > and > [org.apache.camel.ErrorHandlerFactory|https://github.com/apache/camel/blob/afc1eb789c7c0cb3488f8610afe2aa477b366500/dsl/camel-yaml-dsl/camel-yaml-dsl/src/generated/resources/schema/camelYamlDsl.json#L210C8-L210C44] > in camelYamlDsl.json > These elements have same properties and used to define error handler. > What is the goal to have similar classes with different names? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-20667) YAML DSL Consistency question
[ https://issues.apache.org/jira/browse/CAMEL-20667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17836804#comment-17836804 ] Claus Ibsen edited comment on CAMEL-20667 at 4/13/24 10:36 AM: --- The factory is a neutral API for custom error handlers that end users could build and not have dependency on the model classes. was (Author: davsclaus): The factory is for custom error handlers that end users could build and not have dependency on the model classes. > YAML DSL Consistency question > - > > Key: CAMEL-20667 > URL: https://issues.apache.org/jira/browse/CAMEL-20667 > Project: Camel > Issue Type: Improvement > Components: camel-yaml-dsl >Affects Versions: 4.5.0 >Reporter: Marat Gubaidullin >Priority: Minor > > We have > [org.apache.camel.model.ErrorHandlerDefinition|https://github.com/apache/camel/blob/afc1eb789c7c0cb3488f8610afe2aa477b366500/dsl/camel-yaml-dsl/camel-yaml-dsl/src/generated/resources/schema/camelYamlDsl.json#L1461] > and > [org.apache.camel.ErrorHandlerFactory|https://github.com/apache/camel/blob/afc1eb789c7c0cb3488f8610afe2aa477b366500/dsl/camel-yaml-dsl/camel-yaml-dsl/src/generated/resources/schema/camelYamlDsl.json#L210C8-L210C44] > in camelYamlDsl.json > These elements have same properties and used to define error handler. > What is the goal to have similar classes with different names? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20667) YAML DSL Consistency question
[ https://issues.apache.org/jira/browse/CAMEL-20667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17836804#comment-17836804 ] Claus Ibsen commented on CAMEL-20667: - The factory is for custom error handlers that end users could build and not have dependency on the model classes. > YAML DSL Consistency question > - > > Key: CAMEL-20667 > URL: https://issues.apache.org/jira/browse/CAMEL-20667 > Project: Camel > Issue Type: Improvement > Components: camel-yaml-dsl >Affects Versions: 4.5.0 >Reporter: Marat Gubaidullin >Priority: Minor > > We have > [org.apache.camel.model.ErrorHandlerDefinition|https://github.com/apache/camel/blob/afc1eb789c7c0cb3488f8610afe2aa477b366500/dsl/camel-yaml-dsl/camel-yaml-dsl/src/generated/resources/schema/camelYamlDsl.json#L1461] > and > [org.apache.camel.ErrorHandlerFactory|https://github.com/apache/camel/blob/afc1eb789c7c0cb3488f8610afe2aa477b366500/dsl/camel-yaml-dsl/camel-yaml-dsl/src/generated/resources/schema/camelYamlDsl.json#L210C8-L210C44] > in camelYamlDsl.json > These elements have same properties and used to define error handler. > What is the goal to have similar classes with different names? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-20666) RouteDefinition DSL Consistency for XML vs YAML DSL
[ https://issues.apache.org/jira/browse/CAMEL-20666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17836796#comment-17836796 ] Claus Ibsen edited comment on CAMEL-20666 at 4/13/24 10:22 AM: --- TODO: add errorHandler to route *DONE* TODO: we can consider using ErrorHandlerDefinition instead of ErrorHandlerFactory in yaml-schema, then its similar to camel-catalog *WONT FIX* (lets just keep it as-is for now) was (Author: davsclaus): TODO: add errorHandler to route *DONE* TODO: we can consider using ErrorHandlerDefinition instead of ErrorHandlerFactory in yaml-schema, then its similar to camel-catalog > RouteDefinition DSL Consistency for XML vs YAML DSL > --- > > Key: CAMEL-20666 > URL: https://issues.apache.org/jira/browse/CAMEL-20666 > Project: Camel > Issue Type: Improvement > Components: camel-catalog, camel-yaml-dsl >Affects Versions: 4.5.0 >Reporter: Marat Gubaidullin >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.6.0 > > Attachments: Screenshot 2024-04-10 at 4.35.49 PM.png, Screenshot > 2024-04-10 at 4.36.23 PM.png > > > org.apache.camel.model.RouteDefinition in YAML DSL has *errorHandler* > !Screenshot 2024-04-10 at 4.35.49 PM.png! > in camel-catalog there is no *errorHandler* property > !Screenshot 2024-04-10 at 4.36.23 PM.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20666) RouteDefinition DSL Consistency for XML vs YAML DSL
[ https://issues.apache.org/jira/browse/CAMEL-20666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20666: Summary: RouteDefinition DSL Consistency for XML vs YAML DSL (was: RouteDefinition DSL Consistency) > RouteDefinition DSL Consistency for XML vs YAML DSL > --- > > Key: CAMEL-20666 > URL: https://issues.apache.org/jira/browse/CAMEL-20666 > Project: Camel > Issue Type: Improvement > Components: camel-catalog, camel-yaml-dsl >Affects Versions: 4.5.0 >Reporter: Marat Gubaidullin >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.6.0 > > Attachments: Screenshot 2024-04-10 at 4.35.49 PM.png, Screenshot > 2024-04-10 at 4.36.23 PM.png > > > org.apache.camel.model.RouteDefinition in YAML DSL has *errorHandler* > !Screenshot 2024-04-10 at 4.35.49 PM.png! > in camel-catalog there is no *errorHandler* property > !Screenshot 2024-04-10 at 4.36.23 PM.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20665) YAML DSL Inconsistency - StreamCaching vs streamCache
[ https://issues.apache.org/jira/browse/CAMEL-20665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20665: Summary: YAML DSL Inconsistency - StreamCaching vs streamCache (was: DSL Inconsistency) > YAML DSL Inconsistency - StreamCaching vs streamCache > - > > Key: CAMEL-20665 > URL: https://issues.apache.org/jira/browse/CAMEL-20665 > Project: Camel > Issue Type: Improvement > Components: camel-yaml-dsl >Affects Versions: 4.5.0 >Reporter: Marat Gubaidullin >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.6.0 > > > org.apache.camel.model.RouteDefinition has `streamCache` property in > camel-catalog > [route.json|https://github.com/apache/camel/blob/afc1eb789c7c0cb3488f8610afe2aa477b366500/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/models/route.json#L22] > and `streamCaching` in YAML DSL > [camelYamlDsl.json|https://github.com/apache/camel/blob/afc1eb789c7c0cb3488f8610afe2aa477b366500/dsl/camel-yaml-dsl/camel-yaml-dsl/src/generated/resources/schema/camelYamlDsl.json#L5246C12-L5246C25] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20666) RouteDefinition DSL Consistency
[ https://issues.apache.org/jira/browse/CAMEL-20666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17836796#comment-17836796 ] Claus Ibsen commented on CAMEL-20666: - TODO: add errorHandler to route *DONE* TODO: we can consider using ErrorHandlerDefinition instead of ErrorHandlerFactory in yaml-schema, then its similar to camel-catalog > RouteDefinition DSL Consistency > --- > > Key: CAMEL-20666 > URL: https://issues.apache.org/jira/browse/CAMEL-20666 > Project: Camel > Issue Type: Improvement > Components: camel-catalog, camel-yaml-dsl >Affects Versions: 4.5.0 >Reporter: Marat Gubaidullin >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.6.0 > > Attachments: Screenshot 2024-04-10 at 4.35.49 PM.png, Screenshot > 2024-04-10 at 4.36.23 PM.png > > > org.apache.camel.model.RouteDefinition in YAML DSL has *errorHandler* > !Screenshot 2024-04-10 at 4.35.49 PM.png! > in camel-catalog there is no *errorHandler* property > !Screenshot 2024-04-10 at 4.36.23 PM.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20664) camel-mapstruct - MapStruct mappers not found in Spring Boot
[
https://issues.apache.org/jira/browse/CAMEL-20664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20664:
Fix Version/s: 4.6.0
> camel-mapstruct - MapStruct mappers not found in Spring Boot
>
>
> Key: CAMEL-20664
> URL: https://issues.apache.org/jira/browse/CAMEL-20664
> Project: Camel
> Issue Type: Bug
> Components: camel-mapstruct
>Affects Versions: 4.0.0
> Environment: $ java -version
> openjdk version "17.0.7" 2023-04-18
> OpenJDK Runtime Environment Temurin-17.0.7+7 (build 17.0.7+7)
> OpenJDK 64-Bit Server VM Temurin-17.0.7+7 (build 17.0.7+7, mixed mode,
> sharing)
>Reporter: Josh Reagan
>Priority: Minor
> Fix For: 4.6.0
>
> Attachments: camel-mapstruct-demo.zip
>
>
> The `DefaultMapStructFinder` is unable to locate the `Mapper` classes when
> running in Spring Boot. Seems to throw an exception calling
> `PluginHelper.getPackageScanClassResolver(ecc).findByFilter(f ->
> f.getName().endsWith("Mapper"), names);` inside the `doInit()` method.
> You can work around this by creating your own `MapStructFinder`, extending
> `DefaultMapStructFinder`, overriding the `doInit()` function, and calling
> `discoverMappings(...)` with each of your `Mapper` classes. That way it
> doesn't try to scan the classpath to find the `Mapper` classes automatically.
> I've attached a working example to illustrate.
> *Note: It has no issue locating them when running `mvn spring-boot:run`. Only
> when running from the packaged uber jar with `java -jar ...`.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-20665) DSL Inconsistency
[ https://issues.apache.org/jira/browse/CAMEL-20665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-20665: --- Assignee: Claus Ibsen > DSL Inconsistency > - > > Key: CAMEL-20665 > URL: https://issues.apache.org/jira/browse/CAMEL-20665 > Project: Camel > Issue Type: Improvement > Components: camel-yaml-dsl >Affects Versions: 4.5.0 >Reporter: Marat Gubaidullin >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.6.0 > > > org.apache.camel.model.RouteDefinition has `streamCache` property in > camel-catalog > [route.json|https://github.com/apache/camel/blob/afc1eb789c7c0cb3488f8610afe2aa477b366500/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/models/route.json#L22] > and `streamCaching` in YAML DSL > [camelYamlDsl.json|https://github.com/apache/camel/blob/afc1eb789c7c0cb3488f8610afe2aa477b366500/dsl/camel-yaml-dsl/camel-yaml-dsl/src/generated/resources/schema/camelYamlDsl.json#L5246C12-L5246C25] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20665) DSL Inconsistency
[ https://issues.apache.org/jira/browse/CAMEL-20665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20665: Fix Version/s: 4.6.0 > DSL Inconsistency > - > > Key: CAMEL-20665 > URL: https://issues.apache.org/jira/browse/CAMEL-20665 > Project: Camel > Issue Type: Improvement > Components: camel-yaml-dsl >Affects Versions: 4.5.0 >Reporter: Marat Gubaidullin >Priority: Minor > Fix For: 4.6.0 > > > org.apache.camel.model.RouteDefinition has `streamCache` property in > camel-catalog > [route.json|https://github.com/apache/camel/blob/afc1eb789c7c0cb3488f8610afe2aa477b366500/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/models/route.json#L22] > and `streamCaching` in YAML DSL > [camelYamlDsl.json|https://github.com/apache/camel/blob/afc1eb789c7c0cb3488f8610afe2aa477b366500/dsl/camel-yaml-dsl/camel-yaml-dsl/src/generated/resources/schema/camelYamlDsl.json#L5246C12-L5246C25] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20666) RouteDefinition DSL Consistency
[ https://issues.apache.org/jira/browse/CAMEL-20666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20666: Fix Version/s: 4.6.0 > RouteDefinition DSL Consistency > --- > > Key: CAMEL-20666 > URL: https://issues.apache.org/jira/browse/CAMEL-20666 > Project: Camel > Issue Type: Improvement > Components: camel-catalog, camel-yaml-dsl >Affects Versions: 4.5.0 >Reporter: Marat Gubaidullin >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.6.0 > > Attachments: Screenshot 2024-04-10 at 4.35.49 PM.png, Screenshot > 2024-04-10 at 4.36.23 PM.png > > > org.apache.camel.model.RouteDefinition in YAML DSL has *errorHandler* > !Screenshot 2024-04-10 at 4.35.49 PM.png! > in camel-catalog there is no *errorHandler* property > !Screenshot 2024-04-10 at 4.36.23 PM.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20666) RouteDefinition DSL Consistency
[ https://issues.apache.org/jira/browse/CAMEL-20666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17836784#comment-17836784 ] Claus Ibsen commented on CAMEL-20666: - So historically error handling in xml dsl (such as spring xml) would use and that were configured outside routes, and then refer to via ids, eg you would use errorHandlerRef="myErrorHandler" But in Java DSL you could inline the errorHandler directly. Its a bit hard to change this model as JAXB that are used for spring xml has its problems > RouteDefinition DSL Consistency > --- > > Key: CAMEL-20666 > URL: https://issues.apache.org/jira/browse/CAMEL-20666 > Project: Camel > Issue Type: Improvement > Components: camel-catalog, camel-yaml-dsl >Affects Versions: 4.5.0 >Reporter: Marat Gubaidullin >Assignee: Claus Ibsen >Priority: Minor > Attachments: Screenshot 2024-04-10 at 4.35.49 PM.png, Screenshot > 2024-04-10 at 4.36.23 PM.png > > > org.apache.camel.model.RouteDefinition in YAML DSL has *errorHandler* > !Screenshot 2024-04-10 at 4.35.49 PM.png! > in camel-catalog there is no *errorHandler* property > !Screenshot 2024-04-10 at 4.36.23 PM.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20666) RouteDefinition DSL Consistency
[ https://issues.apache.org/jira/browse/CAMEL-20666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-20666: --- Assignee: Claus Ibsen > RouteDefinition DSL Consistency > --- > > Key: CAMEL-20666 > URL: https://issues.apache.org/jira/browse/CAMEL-20666 > Project: Camel > Issue Type: Improvement > Components: camel-catalog, camel-yaml-dsl >Affects Versions: 4.5.0 >Reporter: Marat Gubaidullin >Assignee: Claus Ibsen >Priority: Minor > Attachments: Screenshot 2024-04-10 at 4.35.49 PM.png, Screenshot > 2024-04-10 at 4.36.23 PM.png > > > org.apache.camel.model.RouteDefinition in YAML DSL has *errorHandler* > !Screenshot 2024-04-10 at 4.35.49 PM.png! > in camel-catalog there is no *errorHandler* property > !Screenshot 2024-04-10 at 4.36.23 PM.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20666) RouteDefinition DSL Consistency
[ https://issues.apache.org/jira/browse/CAMEL-20666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17836777#comment-17836777 ] Claus Ibsen commented on CAMEL-20666: - Its the errorHandlerRef that are in the camel-catalog as its the java/xml model. the yaml is a special case, and that yaml schema is even more special > RouteDefinition DSL Consistency > --- > > Key: CAMEL-20666 > URL: https://issues.apache.org/jira/browse/CAMEL-20666 > Project: Camel > Issue Type: Improvement > Components: camel-catalog, camel-yaml-dsl >Affects Versions: 4.5.0 >Reporter: Marat Gubaidullin >Priority: Minor > Attachments: Screenshot 2024-04-10 at 4.35.49 PM.png, Screenshot > 2024-04-10 at 4.36.23 PM.png > > > org.apache.camel.model.RouteDefinition in YAML DSL has *errorHandler* > !Screenshot 2024-04-10 at 4.35.49 PM.png! > in camel-catalog there is no *errorHandler* property > !Screenshot 2024-04-10 at 4.36.23 PM.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20663) camel-main: baseMainSupport may fail to doConfigureCamelContextFromMainConfiguration
[
https://issues.apache.org/jira/browse/CAMEL-20663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20663.
-
Resolution: Fixed
> camel-main: baseMainSupport may fail to
> doConfigureCamelContextFromMainConfiguration
> -
>
> Key: CAMEL-20663
> URL: https://issues.apache.org/jira/browse/CAMEL-20663
> Project: Camel
> Issue Type: Bug
> Components: camel-main
>Affects Versions: 4.4.1
>Reporter: Jiri Ondrusek
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.4.2, 4.6.0
>
>
> According to
> [https://camel.apache.org/manual/camel-4x-upgrade-guide-4_4.html#_camel_main,]
> the property for enabling routeController is
> `{{{}camel.routecontroller.enabled{}}}.` Unfortunatelly if such property is
> used, following code is ignoring it
> ([https://github.com/apache/camel/blob/main/core/camel-main/src/main/java/org/apache/camel/main/BaseMainSupport.java#L1103)]
> - because od lowercase vs camelCase.
>
> If I changethe if to ignore case, I got another error, because value is not
> loaded correctly (in the next lines of the baseMainSupport)
> Problem can be simulated whenrunning test on camel-quarkus-examples/health
> (just change property in this line
> [https://github.com/apache/camel-quarkus-examples/blob/main/health/src/main/resources/application.properties#L31]
> to camel.routeController.enabled = true
>
> I think that more properties might be affected by this error.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20657) Dead observed while redeploying camel bundle in osgi container
[ https://issues.apache.org/jira/browse/CAMEL-20657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20657. - Resolution: Invalid Camel 3.14 is not supported > Dead observed while redeploying camel bundle in osgi container > -- > > Key: CAMEL-20657 > URL: https://issues.apache.org/jira/browse/CAMEL-20657 > Project: Camel > Issue Type: Bug > Components: came-core >Affects Versions: 3.14.7 >Reporter: Deepak >Priority: Major > Attachments: Thread Dump stack trace.txt > > > We use camel 3.14.7 for our integration scenarios. the integration scenarios > are deployed in karaf osgi container. > we recently moved from camel 2x to 3x and we observed that if we try to > redeploy the integration bundle that is already deployed in osgi container. > osgi container first undeploys the existing bundle and redeploys the bundle > again with changes. > when osgi undeploys the bundle camel tries to stop all the service associated > with the bundle that is being undeployed, and we observed that the stop > activity is not getting completed and the other threads that are waiting for > this undeploy to complete is stuck for ever and goes to deadlock state. > I have added the 2 threads stacktrace from the thread dump. > one thread waiting for a lock to deploy a new bundle. while the other thread > has acquired the lock to undeploy the bundle. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20390) camel-zulip: create a component for Zulip
[ https://issues.apache.org/jira/browse/CAMEL-20390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20390: Issue Type: New Feature (was: Task) > camel-zulip: create a component for Zulip > - > > Key: CAMEL-20390 > URL: https://issues.apache.org/jira/browse/CAMEL-20390 > Project: Camel > Issue Type: New Feature >Reporter: Otavio Rodolfo Piske >Priority: Minor > Fix For: 4.x > > > Create a component for interacting with the [Zulip > API|https://camel.zulipchat.com/api/]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20390) camel-zulip: create a component for Zulip
[ https://issues.apache.org/jira/browse/CAMEL-20390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20390: Priority: Minor (was: Major) > camel-zulip: create a component for Zulip > - > > Key: CAMEL-20390 > URL: https://issues.apache.org/jira/browse/CAMEL-20390 > Project: Camel > Issue Type: Task >Reporter: Otavio Rodolfo Piske >Priority: Minor > Fix For: 4.x > > > Create a component for interacting with the [Zulip > API|https://camel.zulipchat.com/api/]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20663) camel-main: baseMainSupport may fail to doConfigureCamelContextFromMainConfiguration
[
https://issues.apache.org/jira/browse/CAMEL-20663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20663:
Priority: Minor (was: Major)
> camel-main: baseMainSupport may fail to
> doConfigureCamelContextFromMainConfiguration
> -
>
> Key: CAMEL-20663
> URL: https://issues.apache.org/jira/browse/CAMEL-20663
> Project: Camel
> Issue Type: Bug
> Components: camel-main
>Affects Versions: 4.4.1
>Reporter: Jiri Ondrusek
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.4.2, 4.6.0
>
>
> According to
> [https://camel.apache.org/manual/camel-4x-upgrade-guide-4_4.html#_camel_main,]
> the property for enabling routeController is
> `{{{}camel.routecontroller.enabled{}}}.` Unfortunatelly if such property is
> used, following code is ignoring it
> ([https://github.com/apache/camel/blob/main/core/camel-main/src/main/java/org/apache/camel/main/BaseMainSupport.java#L1103)]
> - because od lowercase vs camelCase.
>
> If I changethe if to ignore case, I got another error, because value is not
> loaded correctly (in the next lines of the baseMainSupport)
> Problem can be simulated whenrunning test on camel-quarkus-examples/health
> (just change property in this line
> [https://github.com/apache/camel-quarkus-examples/blob/main/health/src/main/resources/application.properties#L31]
> to camel.routeController.enabled = true
>
> I think that more properties might be affected by this error.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20663) camel-main: baseMainSupport may fail to doConfigureCamelContextFromMainConfiguration
[
https://issues.apache.org/jira/browse/CAMEL-20663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20663:
Fix Version/s: 4.4.2
> camel-main: baseMainSupport may fail to
> doConfigureCamelContextFromMainConfiguration
> -
>
> Key: CAMEL-20663
> URL: https://issues.apache.org/jira/browse/CAMEL-20663
> Project: Camel
> Issue Type: Bug
> Components: camel-main
>Affects Versions: 4.4.1
>Reporter: Jiri Ondrusek
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.4.2, 4.6.0
>
>
> According to
> [https://camel.apache.org/manual/camel-4x-upgrade-guide-4_4.html#_camel_main,]
> the property for enabling routeController is
> `{{{}camel.routecontroller.enabled{}}}.` Unfortunatelly if such property is
> used, following code is ignoring it
> ([https://github.com/apache/camel/blob/main/core/camel-main/src/main/java/org/apache/camel/main/BaseMainSupport.java#L1103)]
> - because od lowercase vs camelCase.
>
> If I changethe if to ignore case, I got another error, because value is not
> loaded correctly (in the next lines of the baseMainSupport)
> Problem can be simulated whenrunning test on camel-quarkus-examples/health
> (just change property in this line
> [https://github.com/apache/camel-quarkus-examples/blob/main/health/src/main/resources/application.properties#L31]
> to camel.routeController.enabled = true
>
> I think that more properties might be affected by this error.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20663) camel-main: baseMainSupport may fail to doConfigureCamelContextFromMainConfiguration
[
https://issues.apache.org/jira/browse/CAMEL-20663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20663:
Fix Version/s: 4.6.0
> camel-main: baseMainSupport may fail to
> doConfigureCamelContextFromMainConfiguration
> -
>
> Key: CAMEL-20663
> URL: https://issues.apache.org/jira/browse/CAMEL-20663
> Project: Camel
> Issue Type: Bug
> Components: camel-main
>Affects Versions: 4.4.1
>Reporter: Jiri Ondrusek
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.6.0
>
>
> According to
> [https://camel.apache.org/manual/camel-4x-upgrade-guide-4_4.html#_camel_main,]
> the property for enabling routeController is
> `{{{}camel.routecontroller.enabled{}}}.` Unfortunatelly if such property is
> used, following code is ignoring it
> ([https://github.com/apache/camel/blob/main/core/camel-main/src/main/java/org/apache/camel/main/BaseMainSupport.java#L1103)]
> - because od lowercase vs camelCase.
>
> If I changethe if to ignore case, I got another error, because value is not
> loaded correctly (in the next lines of the baseMainSupport)
> Problem can be simulated whenrunning test on camel-quarkus-examples/health
> (just change property in this line
> [https://github.com/apache/camel-quarkus-examples/blob/main/health/src/main/resources/application.properties#L31]
> to camel.routeController.enabled = true
>
> I think that more properties might be affected by this error.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-20663) camel-main: baseMainSupport may fail to doConfigureCamelContextFromMainConfiguration
[
https://issues.apache.org/jira/browse/CAMEL-20663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-20663:
---
Assignee: Claus Ibsen
> camel-main: baseMainSupport may fail to
> doConfigureCamelContextFromMainConfiguration
> -
>
> Key: CAMEL-20663
> URL: https://issues.apache.org/jira/browse/CAMEL-20663
> Project: Camel
> Issue Type: Bug
> Components: camel-main
>Affects Versions: 4.4.1
>Reporter: Jiri Ondrusek
>Assignee: Claus Ibsen
>Priority: Major
>
> According to
> [https://camel.apache.org/manual/camel-4x-upgrade-guide-4_4.html#_camel_main,]
> the property for enabling routeController is
> `{{{}camel.routecontroller.enabled{}}}.` Unfortunatelly if such property is
> used, following code is ignoring it
> ([https://github.com/apache/camel/blob/main/core/camel-main/src/main/java/org/apache/camel/main/BaseMainSupport.java#L1103)]
> - because od lowercase vs camelCase.
>
> If I changethe if to ignore case, I got another error, because value is not
> loaded correctly (in the next lines of the baseMainSupport)
> Problem can be simulated whenrunning test on camel-quarkus-examples/health
> (just change property in this line
> [https://github.com/apache/camel-quarkus-examples/blob/main/health/src/main/resources/application.properties#L31]
> to camel.routeController.enabled = true
>
> I think that more properties might be affected by this error.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20521) camel-amqp - AMQP publisher application is losing messages with local JMS transaction enabled
[
https://issues.apache.org/jira/browse/CAMEL-20521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17836773#comment-17836773
]
Claus Ibsen commented on CAMEL-20521:
-
We need to upgrade spring in the 4.0.x 3.22.x and 3.21.x branches. PRs is
weclome
> camel-amqp - AMQP publisher application is losing messages with local JMS
> transaction enabled
> -
>
> Key: CAMEL-20521
> URL: https://issues.apache.org/jira/browse/CAMEL-20521
> Project: Camel
> Issue Type: Bug
> Components: camel-amqp
>Affects Versions: 4.4.0
>Reporter: Luigi De Masi
>Assignee: Luigi De Masi
>Priority: Major
> Fix For: 4.0.5, 4.4.2, 4.6.0
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> camel-amqp with local transaction enabled loses messages because to invoke
> the commit, it uses a spring-jms routine that catch and ignore a couple of
> exceptions that occurs and should not be ignored:
> In {{org.apache.camel.component.jms.JmsConfiguration.CamelJmsTemplate}} :
> !screenshot-1.png!
> that calls {{org.springframework.jms.support.JmsUtils}}
> !screenshot-2.png!
> In the comment it says that {{jakarta.jms.TransactionInProgressException}}
> and {{jakarta.jms.IllegalStateException}} can only happen in case of a JTA
> transaction but it can happens
> also in case of connection problems:
> {code:java}
> javax.jms.IllegalStateException: The Session is closed
> at org.apache.qpid.jms.JmsSession.checkClosed(JmsSession.java:1113)
> at org.apache.qpid.jms.JmsSession.getTransacted(JmsSession.java:213)
> at
> org.messaginghub.pooled.jms.JmsPoolSession.getTransacted(JmsPoolSession.java:256)
> at
> nl.ns.hip.cci.jms.CamelJmsTemplate.doSendToDestination(CamelJmsTemplate.java:94)
> at
> nl.ns.hip.cci.jms.CamelJmsTemplate.lambda$send$0(CamelJmsTemplate.java:33)
> at
> org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:504)
> at nl.ns.hip.cci.jms.CamelJmsTemplate.send(CamelJmsTemplate.java:31)
> at
> org.apache.camel.component.jms.JmsProducer.doSend(JmsProducer.java:425)
> at
> org.apache.camel.component.jms.JmsProducer.processInOnly(JmsProducer.java:392)
> at
> org.apache.camel.component.jms.JmsProducer.process(JmsProducer.java:159)
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:172)
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.doRun(RedeliveryErrorHandler.java:818)
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.run(RedeliveryErrorHandler.java:726)
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:181)
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:59)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:165)
> at
> org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:392)
> at
> org.apache.camel.component.seda.SedaConsumer.sendToConsumers(SedaConsumer.java:269)
> at
> org.apache.camel.component.seda.SedaConsumer.doRun(SedaConsumer.java:187)
> at
> org.apache.camel.component.seda.SedaConsumer.run(SedaConsumer.java:130)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:829)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
