[jira] [Created] (CAMEL-21255) camel-core - Add listener for creating ThreadFactory in ExecutorServiceManager
Claus Ibsen created CAMEL-21255: --- Summary: camel-core - Add listener for creating ThreadFactory in ExecutorServiceManager Key: CAMEL-21255 URL: https://issues.apache.org/jira/browse/CAMEL-21255 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 4.4.4, 4.8.1, 4.9.0 This is needed to allow to trap when a ThreadFactory is created to be able to control some custom behavior needed by camel-opentelemetry. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21230) camel-spring-boot - Upgrade to SB 3.2.10
[ https://issues.apache.org/jira/browse/CAMEL-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-21230. - Resolution: Fixed > camel-spring-boot - Upgrade to SB 3.2.10 > > > Key: CAMEL-21230 > URL: https://issues.apache.org/jira/browse/CAMEL-21230 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.4.4 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21230) camel-spring-boot - Upgrade to SB 3.2.10
[ https://issues.apache.org/jira/browse/CAMEL-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883910#comment-17883910 ] Claus Ibsen edited comment on CAMEL-21230 at 9/24/24 5:16 AM: -- Upgrade to Jetty 12.0.13 may need some other fix Those are fixed via CAMEL-20830 was (Author: davsclaus): TODO: Upgrade to Jetty 12.0.13 may need some other fix > camel-spring-boot - Upgrade to SB 3.2.10 > > > Key: CAMEL-21230 > URL: https://issues.apache.org/jira/browse/CAMEL-21230 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.4.4 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21252) Add checking for non .*-versions to sync-properties-maven-plugin
[
https://issues.apache.org/jira/browse/CAMEL-21252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17884111#comment-17884111
]
Claus Ibsen commented on CAMEL-21252:
-
We use dash in the Camel naming style so it should be zeebe-version
> Add checking for non .*-versions to sync-properties-maven-plugin
>
>
> Key: CAMEL-21252
> URL: https://issues.apache.org/jira/browse/CAMEL-21252
> Project: Camel
> Issue Type: Bug
> Components: tooling
>Affects Versions: 4.8.0
>Reporter: Thomas Cunningham
>Assignee: Thomas Cunningham
>Priority: Major
>
> sync-properties-maven-plugin only synchronizes properties that fit the
> pattern
> {code:java}
> @Parameter(defaultValue = ".*-version") {code}
> which means that properties like
> {code:java}
> 8.5.7 {code}
> [https://github.com/apache/camel/blob/main/parent/pom.xml#L504C9-L504C45]
> are allowed but do not get synced to camel-dependencies. I'd like to add
> a check for properties not meeting that pattern and fix the zeebe.version->
> zeebe-version so that it gets generated in camel-dependencies.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21252) Add checking for non .*-versions to sync-properties-maven-plugin
[
https://issues.apache.org/jira/browse/CAMEL-21252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21252:
Issue Type: Task (was: Bug)
> Add checking for non .*-versions to sync-properties-maven-plugin
>
>
> Key: CAMEL-21252
> URL: https://issues.apache.org/jira/browse/CAMEL-21252
> Project: Camel
> Issue Type: Task
> Components: tooling
>Affects Versions: 4.8.0
>Reporter: Thomas Cunningham
>Assignee: Thomas Cunningham
>Priority: Major
>
> sync-properties-maven-plugin only synchronizes properties that fit the
> pattern
> {code:java}
> @Parameter(defaultValue = ".*-version") {code}
> which means that properties like
> {code:java}
> 8.5.7 {code}
> [https://github.com/apache/camel/blob/main/parent/pom.xml#L504C9-L504C45]
> are allowed but do not get synced to camel-dependencies. I'd like to add
> a check for properties not meeting that pattern and fix the zeebe.version->
> zeebe-version so that it gets generated in camel-dependencies.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21230) camel-spring-boot - Upgrade to SB 3.2.10
[ https://issues.apache.org/jira/browse/CAMEL-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883910#comment-17883910 ] Claus Ibsen commented on CAMEL-21230: - TODO: Upgrade to Jetty 12.0.13 may need some other fix > camel-spring-boot - Upgrade to SB 3.2.10 > > > Key: CAMEL-21230 > URL: https://issues.apache.org/jira/browse/CAMEL-21230 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.4.4 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21250) camel-report-maven-plugin - Can we cover anonymous routes if loaded from xml files
[ https://issues.apache.org/jira/browse/CAMEL-21250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21250: Priority: Minor (was: Major) > camel-report-maven-plugin - Can we cover anonymous routes if loaded from xml > files > -- > > Key: CAMEL-21250 > URL: https://issues.apache.org/jira/browse/CAMEL-21250 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > > When using camel-report:route-coverage and you have many routes in XML files > without route ids, then they are not correlated in coverage data. Maybe we > can find a wat to make this possible for anonymous routes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-21230) camel-spring-boot - Upgrade to SB 3.2.10
[ https://issues.apache.org/jira/browse/CAMEL-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-21230: --- Assignee: Claus Ibsen > camel-spring-boot - Upgrade to SB 3.2.10 > > > Key: CAMEL-21230 > URL: https://issues.apache.org/jira/browse/CAMEL-21230 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.4.4 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21250) camel-report-maven-plugin - Can we cover anonymous routes if loaded from xml files
[ https://issues.apache.org/jira/browse/CAMEL-21250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21250: Component/s: tooling > camel-report-maven-plugin - Can we cover anonymous routes if loaded from xml > files > -- > > Key: CAMEL-21250 > URL: https://issues.apache.org/jira/browse/CAMEL-21250 > Project: Camel > Issue Type: Improvement > Components: tooling >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > > When using camel-report:route-coverage and you have many routes in XML files > without route ids, then they are not correlated in coverage data. Maybe we > can find a wat to make this possible for anonymous routes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21250) camel-report-maven-plugin - Can we cover anonymous routes if loaded from xml files
Claus Ibsen created CAMEL-21250: --- Summary: camel-report-maven-plugin - Can we cover anonymous routes if loaded from xml files Key: CAMEL-21250 URL: https://issues.apache.org/jira/browse/CAMEL-21250 Project: Camel Issue Type: Improvement Reporter: Claus Ibsen Assignee: Claus Ibsen When using camel-report:route-coverage and you have many routes in XML files without route ids, then they are not correlated in coverage data. Maybe we can find a wat to make this possible for anonymous routes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21239) camel-report-maven-plugin - NPE if route does not have id
[
https://issues.apache.org/jira/browse/CAMEL-21239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883731#comment-17883731
]
Claus Ibsen edited comment on CAMEL-21239 at 9/23/24 7:27 AM:
--
Okay I have fixed so all the data is now in the report
{code:java}
[INFO] --- camel-report:4.9.0-SNAPSHOT:route-coverage (default-cli) @
camel-example-spring-boot ---
[INFO] Discovered 1 routes
[INFO] Route coverage summary:Class: sample.camel.MyCamelRouter
Route: hello Line # Count Route
-- - -
38 1 from
40 1 bean
42 1 to
Coverage: 3 out of 3 (100.0% / threshold 100.0%)
Status: Success
[INFO]
[INFO] Overall coverage summary:Coverage: 3 out of 3 (100.0% / threshold 0.0%)
Status: Success {code}
was (Author: davsclaus):
Okay I have fixed so all the data is now in the report
{code:java}
[INFO] --- camel-report:4.9.0-SNAPSHOT:route-coverage (default-cli) @
camel-example-spring-boot ---
[INFO] Discovered 1 routes
[INFO] Route coverage summary:Class: sample.camel.MyCamelRouter
Route: hello Line # Count Route
-- - -
38 1 from
40 1 bean
42 1 toCoverage: 3 out of 3 (100.0% / threshold 100.0%)
Status: Success
[INFO]
[INFO] Overall coverage summary:Coverage: 3 out of 3 (100.0% / threshold 0.0%)
Status: Success {code}
> camel-report-maven-plugin - NPE if route does not have id
> -
>
> Key: CAMEL-21239
> URL: https://issues.apache.org/jira/browse/CAMEL-21239
> Project: Camel
> Issue Type: Bug
> Components: tooling
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.4.4, 4.8.1, 4.9.0
>
>
> Caused by: java.lang.NullPointerException: Cannot invoke
> "org.w3c.dom.Node.getNodeValue()" because the return value of
> "org.w3c.dom.NamedNodeMap.getNamedItem(String)" is null
> at
> org.apache.camel.parser.helper.RouteCoverageHelper.parseDumpRouteCoverageByRouteId
> (RouteCoverageHelper.java:70)
> at org.apache.camel.maven.RouteCoverageMojo.grabDumpData
> (RouteCoverageMojo.java:263)
> at org.apache.camel.maven.RouteCoverageMojo.execute
> (RouteCoverageMojo.java:228)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21239) camel-report-maven-plugin - NPE if route does not have id
[
https://issues.apache.org/jira/browse/CAMEL-21239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883731#comment-17883731
]
Claus Ibsen commented on CAMEL-21239:
-
Okay I have fixed so all the data is now in the report
{code:java}
[INFO] --- camel-report:4.9.0-SNAPSHOT:route-coverage (default-cli) @
camel-example-spring-boot ---
[INFO] Discovered 1 routes
[INFO] Route coverage summary:Class: sample.camel.MyCamelRouter
Route: hello Line # Count Route
-- - -
38 1 from
40 1 bean
42 1 toCoverage: 3 out of 3 (100.0% / threshold 100.0%)
Status: Success
[INFO]
[INFO] Overall coverage summary:Coverage: 3 out of 3 (100.0% / threshold 0.0%)
Status: Success {code}
> camel-report-maven-plugin - NPE if route does not have id
> -
>
> Key: CAMEL-21239
> URL: https://issues.apache.org/jira/browse/CAMEL-21239
> Project: Camel
> Issue Type: Bug
> Components: tooling
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.4.4, 4.8.1, 4.9.0
>
>
> Caused by: java.lang.NullPointerException: Cannot invoke
> "org.w3c.dom.Node.getNodeValue()" because the return value of
> "org.w3c.dom.NamedNodeMap.getNamedItem(String)" is null
> at
> org.apache.camel.parser.helper.RouteCoverageHelper.parseDumpRouteCoverageByRouteId
> (RouteCoverageHelper.java:70)
> at org.apache.camel.maven.RouteCoverageMojo.grabDumpData
> (RouteCoverageMojo.java:263)
> at org.apache.camel.maven.RouteCoverageMojo.execute
> (RouteCoverageMojo.java:228)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21247) camel-core - CamelThreadFactory should create thread via newer JDK api
[ https://issues.apache.org/jira/browse/CAMEL-21247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-21247. - Resolution: Implemented > camel-core - CamelThreadFactory should create thread via newer JDK api > -- > > Key: CAMEL-21247 > URL: https://issues.apache.org/jira/browse/CAMEL-21247 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.9.0 > > > In CamelThreadFactory then we use new Thread... code. > However to prepare for JDK21 virtual threads, we should create it via > Thread.platformOf vs Virtual Threads. (require JDK21 runtime) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21247) camel-core - CamelThreadFactory should create thread via newer JDK api
[ https://issues.apache.org/jira/browse/CAMEL-21247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883569#comment-17883569 ] Claus Ibsen edited comment on CAMEL-21247 at 9/22/24 6:39 AM: -- Ah yeah that seems its already there. And just to be sure, this class will only be in the JAR if the project is built with a JDK21 compiler. And the Camel releases are now done with that. was (Author: davsclaus): Ah yeah that seems its already there. And just to be sure, this class will only be in the JAR if the project is built with a JDK21 compiler. > camel-core - CamelThreadFactory should create thread via newer JDK api > -- > > Key: CAMEL-21247 > URL: https://issues.apache.org/jira/browse/CAMEL-21247 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.9.0 > > > In CamelThreadFactory then we use new Thread... code. > However to prepare for JDK21 virtual threads, we should create it via > Thread.platformOf vs Virtual Threads. (require JDK21 runtime) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21247) camel-core - CamelThreadFactory should create thread via newer JDK api
[ https://issues.apache.org/jira/browse/CAMEL-21247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883569#comment-17883569 ] Claus Ibsen commented on CAMEL-21247: - Ah yeah that seems its already there. And just to be sure, this class will only be in the JAR if the project is built with a JDK21 compiler. > camel-core - CamelThreadFactory should create thread via newer JDK api > -- > > Key: CAMEL-21247 > URL: https://issues.apache.org/jira/browse/CAMEL-21247 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.9.0 > > > In CamelThreadFactory then we use new Thread... code. > However to prepare for JDK21 virtual threads, we should create it via > Thread.platformOf vs Virtual Threads. (require JDK21 runtime) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21247) camel-core - CamelThreadFactory should create thread via newer JDK api
[ https://issues.apache.org/jira/browse/CAMEL-21247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883460#comment-17883460 ] Claus Ibsen commented on CAMEL-21247: - Mind that this may be JDK21 only and we use 17 as base-line, so this may be not so easy. > camel-core - CamelThreadFactory should create thread via newer JDK api > -- > > Key: CAMEL-21247 > URL: https://issues.apache.org/jira/browse/CAMEL-21247 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.9.0 > > > In CamelThreadFactory then we use new Thread... code. > However to prepare for JDK21 virtual threads, we should create it via > Thread.platformOf vs Virtual Threads. (require JDK21 runtime) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21247) camel-core - CamelThreadFactory should create thread via newer JDK api
Claus Ibsen created CAMEL-21247: --- Summary: camel-core - CamelThreadFactory should create thread via newer JDK api Key: CAMEL-21247 URL: https://issues.apache.org/jira/browse/CAMEL-21247 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Fix For: 4.9.0 In CamelThreadFactory then we use new Thread... code. However to prepare for JDK21 virtual threads, we should create it via Thread.platformOf vs Virtual Threads. (require JDK21 runtime) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21246) camel-jbang - Export should include console & management if dev console is enabled
[ https://issues.apache.org/jira/browse/CAMEL-21246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-21246. - Fix Version/s: 4.8.1 Resolution: Fixed > camel-jbang - Export should include console & management if dev console is > enabled > -- > > Key: CAMEL-21246 > URL: https://issues.apache.org/jira/browse/CAMEL-21246 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.8.1, 4.9.0 > > > Enabling via > camel.main.devConsoleEnabled = true > camel.server.devConsoleEnabled = true > > Should add dependency > camel-console > camel-management -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21244) camel-clickup
[
https://issues.apache.org/jira/browse/CAMEL-21244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21244:
Fix Version/s: 4.9.0
> camel-clickup
> -
>
> Key: CAMEL-21244
> URL: https://issues.apache.org/jira/browse/CAMEL-21244
> Project: Camel
> Issue Type: New Feature
>Reporter: Nicolò Scarpa
>Priority: Major
> Fix For: 4.9.0
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> A new Camel component to receive events from webhooks by adopting the
> {{camel-webhook}} meta-component.
> ClickUp developer guide for webhooks:
> [https://clickup.com/api/developer-portal/webhooks/]
> The component may be further extended to support read/write to ClickUp REST
> APIs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-21243) camel-braintree-starter tries to use org.osgi:org.osgi.core:8.0.0
[
https://issues.apache.org/jira/browse/CAMEL-21243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-21243:
---
Assignee: Thomas Cunningham
> camel-braintree-starter tries to use org.osgi:org.osgi.core:8.0.0
> -
>
> Key: CAMEL-21243
> URL: https://issues.apache.org/jira/browse/CAMEL-21243
> Project: Camel
> Issue Type: Bug
> Components: camel-braintree, camel-spring-boot
>Affects Versions: 4.8.0
>Reporter: Thomas Cunningham
>Assignee: Thomas Cunningham
>Priority: Major
> Fix For: 4.8.1, 4.9.0
>
>
> I get the following error trying to build camel-braintree-starter
> {code:java}
> [INFO] < org.apache.camel.springboot:camel-braintree-starter
> >-
> [INFO] Building Camel SB Starters :: Braintree 4.9.0-SNAPSHOT
> [INFO] from pom.xml
> [INFO] [ jar
> ]-
> [WARNING] The POM for org.osgi:org.osgi.core:jar:8.0.0 is missing, no
> dependency information available
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.492 s
> [INFO] Finished at: 2024-09-19T07:48:51-04:00
> [INFO]
>
> [ERROR] Failed to execute goal on project camel-braintree-starter: Could not
> resolve dependencies for project
> org.apache.camel.springboot:camel-braintree-starter:jar:4.9.0-SNAPSHOT
> [ERROR] dependency: org.osgi:org.osgi.core:jar:8.0.0 (compile)
> [ERROR] org.osgi:org.osgi.core:jar:8.0.0 was not found in
> http://10.0.144.111:8081/repository/maven-public/ during a previous attempt.
> This failure was cached in the local repository and resolution is not
> reattempted until the update interval of fuse-repository has elapsed or
> updates are forced
> [ERROR]{code}
> It looks like org.osgi:org.osgi.core:8.0.0 does not exist - the last version
> was 6.0.0, and then it was renamed to org.osgi:osgi.core -
> [https://mvnrepository.com/artifact/org.osgi/osgi.core]
>
> com.braintreepayments.gateway:braintree-java:3.35.0 uses
> org.osgi:org.osgi.core:4.2.0
> [https://repo1.maven.org/maven2/com/braintreepayments/gateway/braintree-java/3.35.0/braintree-java-3.35.0.pom]
> but my guess is something wrong with the manifest settings? I'd like to
> add a dependencyManagement entry to force use of org.osgi:org.osgi.core:4.2.0
> so that camel-braintree-starter compiles.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21243) camel-braintree-starter tries to use org.osgi:org.osgi.core:8.0.0
[
https://issues.apache.org/jira/browse/CAMEL-21243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-21243.
-
Resolution: Fixed
> camel-braintree-starter tries to use org.osgi:org.osgi.core:8.0.0
> -
>
> Key: CAMEL-21243
> URL: https://issues.apache.org/jira/browse/CAMEL-21243
> Project: Camel
> Issue Type: Bug
> Components: camel-braintree, camel-spring-boot
>Affects Versions: 4.8.0
>Reporter: Thomas Cunningham
>Assignee: Thomas Cunningham
>Priority: Major
> Fix For: 4.8.1, 4.9.0
>
>
> I get the following error trying to build camel-braintree-starter
> {code:java}
> [INFO] < org.apache.camel.springboot:camel-braintree-starter
> >-
> [INFO] Building Camel SB Starters :: Braintree 4.9.0-SNAPSHOT
> [INFO] from pom.xml
> [INFO] [ jar
> ]-
> [WARNING] The POM for org.osgi:org.osgi.core:jar:8.0.0 is missing, no
> dependency information available
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.492 s
> [INFO] Finished at: 2024-09-19T07:48:51-04:00
> [INFO]
>
> [ERROR] Failed to execute goal on project camel-braintree-starter: Could not
> resolve dependencies for project
> org.apache.camel.springboot:camel-braintree-starter:jar:4.9.0-SNAPSHOT
> [ERROR] dependency: org.osgi:org.osgi.core:jar:8.0.0 (compile)
> [ERROR] org.osgi:org.osgi.core:jar:8.0.0 was not found in
> http://10.0.144.111:8081/repository/maven-public/ during a previous attempt.
> This failure was cached in the local repository and resolution is not
> reattempted until the update interval of fuse-repository has elapsed or
> updates are forced
> [ERROR]{code}
> It looks like org.osgi:org.osgi.core:8.0.0 does not exist - the last version
> was 6.0.0, and then it was renamed to org.osgi:osgi.core -
> [https://mvnrepository.com/artifact/org.osgi/osgi.core]
>
> com.braintreepayments.gateway:braintree-java:3.35.0 uses
> org.osgi:org.osgi.core:4.2.0
> [https://repo1.maven.org/maven2/com/braintreepayments/gateway/braintree-java/3.35.0/braintree-java-3.35.0.pom]
> but my guess is something wrong with the manifest settings? I'd like to
> add a dependencyManagement entry to force use of org.osgi:org.osgi.core:4.2.0
> so that camel-braintree-starter compiles.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-21246) camel-jbang - Export should include console & management if dev console is enabled
Claus Ibsen created CAMEL-21246: --- Summary: camel-jbang - Export should include console & management if dev console is enabled Key: CAMEL-21246 URL: https://issues.apache.org/jira/browse/CAMEL-21246 Project: Camel Issue Type: Improvement Components: camel-jbang Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 4.9.0 Enabling via camel.main.devConsoleEnabled = true camel.server.devConsoleEnabled = true Should add dependency camel-console camel-management -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-21216) Apache Camel LRA does not work with Oracle MicroTX LRA coordinator
[
https://issues.apache.org/jira/browse/CAMEL-21216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-21216:
---
Assignee: Zheng Feng
> Apache Camel LRA does not work with Oracle MicroTX LRA coordinator
> --
>
> Key: CAMEL-21216
> URL: https://issues.apache.org/jira/browse/CAMEL-21216
> Project: Camel
> Issue Type: Bug
> Components: camel-lra
>Affects Versions: 4.7.0
>Reporter: Dirk Fiedler
>Assignee: Zheng Feng
>Priority: Minor
> Fix For: 4.x
>
>
> {color:#00}Hi Team,{color}
> {color:#00}we are using the Apache Camel LRA components within Java
> Springboot projects to implement saga services.{color}
> {color:#00}Till now, we are using Narayana as an LRA-Coordinator. Now we
> want to switch to Oracl MicroTX {color}
> {color:#00}(https://docs.oracle.com/en/database/oracle/transaction-manager-for-microservices/24.2/tmmdg/lra-transaction-protocol.html).{color}
> {color:#00}After configuring Oracle MircoTX instead of Narayana, we are
> facing two problems within the {color}
> {color:#00}Apache Camel LRA component code.{color}
> {color:#0451a5}1){color}{color:#00} While joining an LRA Transaction, the
> payload sent by Apache Camel is URL encoded{color}
> {color:#0451a5}2){color}{color:#00} The Query parameter sent by Oracle
> LRA coordinator are url encoded, but will not be decoded by Apache Camal LRA
> (see also: CAMEL-21197){color}
> {color:#00}I will set up a branch with my suggested code changes and link
> this afterwards to this jira bug.{color}
> {color:#00}The code changes are completely backwards compatible with
> Narayana (already tested).{color}
> {color:#0451a5}1){color}{color:#00} Joining an LRA Transaction{color}
> {color:#00}The class 'LRAClient' is using 'LRAUrlBuilder' inside Method
> 'join'. All parts of the http put body are url encoded. {color}
> {color:#00}Within Oracle LRA Coordinator log i can see the incomming
> request from Apache Camel:{color}
>
> {code:java}
> ;
>
> rel=compensate,;
> rel=complete{code}
> {color:#00}This url encoded query param
> 'Camel-Saga-Complete=direct%3A%2F%2Fsaga1_sagaService_complete' will be
> encoded again on Oracle LRA Coordinator side.{color}
> {color:#00}This is causing the error message within Apache Camel
> LRA:{color}
>
> {code:java}
> o.a.c.RuntimeCamelException: Cannot join LRA at
> o.a.c.s.l.LRAClient.lambda$join$2(LRAClient.java:138) ... 10 common frames
> omitted Wrapped by: j.u.c.CompletionException:
> org.apache.camel.RuntimeCamelException: Cannot join LRA at
> j.u.c.CompletableFuture.encodeThrowable(Unknown Source) at
> j.u.c.CompletableFuture.completeThrowable(Unknown Source) at
> j.u.c.CompletableFuture$UniApply.tryFire(Unknown Source) at
> j.u.c.CompletableFuture.postComplete(Unknown Source) at
> j.u.c.CompletableFuture.postFire(Unknown Source) at
> j.u.c.CompletableFuture$UniWhenComplete.tryFire(Unknown Source) at
> j.u.c.CompletableFuture$Completion.exec(Unknown Source) at
> j.u.c.ForkJoinTask.doExec(Unknown Source) at
> j.u.c.ForkJoinPool$WorkQueue.topLevelExec(Unknown Source) at
> j.u.c.ForkJoinPool.scan(Unknown Source) at
> j.u.c.ForkJoinPool.runWorker(Unknown Source) at
> j.u.c.ForkJoinWorkerThread.run(Unknown Source){code}
>
> {color:#00}When logging the result http code and body{color}
>
> {code:java}
> LOG.error("error while joining LRA: {} / {}", response.statusCode(),
> response.body());{code}
> {color:#00}i am getting this:{color}
> {code:java}
> error while joining LRA: 400 / error: URL is double encoded{code}
> {color:#00}The problem can be solved by not url encoding the given urls
> within the joinLRA payload.{color}
>
> org.apache.camel.service.lra.LRAUrlBuilder -> query:
>
> This code should not be executed:
>
> {code:java}
> key = URLEncoder.encode(toNonnullString(key), StandardCharsets.UTF_8.name());
> value = URLEncoder.encode(toNonnullString(value),
> StandardCharsets.UTF_8.name());
> {code}
>
> {color:#0451a5}2){color}{color:#00} Decode given query parameter from
> Oracle LRA-Coordinator call{color}
> {color:#00}After solving 1), i am getting a new exception:{color}
> {code:java}
> j.l.IllegalArgumentException: URI direct%3A%2F%2Fsaga1_sagaService_complete
> is not allowed at
> o.a.c.s.l.LRASagaRoutes.verifyRequest(LRASagaRoutes.java:107) at
> o.a.c.s.p.DelegateSyncProcessor.process(DelegateSyncProcessor.java:65) at
> o.
[jira] [Updated] (CAMEL-21216) Apache Camel LRA does not work with Oracle MicroTX LRA coordinator
[
https://issues.apache.org/jira/browse/CAMEL-21216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21216:
Fix Version/s: 4.8.1
4.9.0
(was: 4.x)
> Apache Camel LRA does not work with Oracle MicroTX LRA coordinator
> --
>
> Key: CAMEL-21216
> URL: https://issues.apache.org/jira/browse/CAMEL-21216
> Project: Camel
> Issue Type: Bug
> Components: camel-lra
>Affects Versions: 4.7.0
>Reporter: Dirk Fiedler
>Assignee: Zheng Feng
>Priority: Minor
> Fix For: 4.8.1, 4.9.0
>
>
> {color:#00}Hi Team,{color}
> {color:#00}we are using the Apache Camel LRA components within Java
> Springboot projects to implement saga services.{color}
> {color:#00}Till now, we are using Narayana as an LRA-Coordinator. Now we
> want to switch to Oracl MicroTX {color}
> {color:#00}(https://docs.oracle.com/en/database/oracle/transaction-manager-for-microservices/24.2/tmmdg/lra-transaction-protocol.html).{color}
> {color:#00}After configuring Oracle MircoTX instead of Narayana, we are
> facing two problems within the {color}
> {color:#00}Apache Camel LRA component code.{color}
> {color:#0451a5}1){color}{color:#00} While joining an LRA Transaction, the
> payload sent by Apache Camel is URL encoded{color}
> {color:#0451a5}2){color}{color:#00} The Query parameter sent by Oracle
> LRA coordinator are url encoded, but will not be decoded by Apache Camal LRA
> (see also: CAMEL-21197){color}
> {color:#00}I will set up a branch with my suggested code changes and link
> this afterwards to this jira bug.{color}
> {color:#00}The code changes are completely backwards compatible with
> Narayana (already tested).{color}
> {color:#0451a5}1){color}{color:#00} Joining an LRA Transaction{color}
> {color:#00}The class 'LRAClient' is using 'LRAUrlBuilder' inside Method
> 'join'. All parts of the http put body are url encoded. {color}
> {color:#00}Within Oracle LRA Coordinator log i can see the incomming
> request from Apache Camel:{color}
>
> {code:java}
> ;
>
> rel=compensate,;
> rel=complete{code}
> {color:#00}This url encoded query param
> 'Camel-Saga-Complete=direct%3A%2F%2Fsaga1_sagaService_complete' will be
> encoded again on Oracle LRA Coordinator side.{color}
> {color:#00}This is causing the error message within Apache Camel
> LRA:{color}
>
> {code:java}
> o.a.c.RuntimeCamelException: Cannot join LRA at
> o.a.c.s.l.LRAClient.lambda$join$2(LRAClient.java:138) ... 10 common frames
> omitted Wrapped by: j.u.c.CompletionException:
> org.apache.camel.RuntimeCamelException: Cannot join LRA at
> j.u.c.CompletableFuture.encodeThrowable(Unknown Source) at
> j.u.c.CompletableFuture.completeThrowable(Unknown Source) at
> j.u.c.CompletableFuture$UniApply.tryFire(Unknown Source) at
> j.u.c.CompletableFuture.postComplete(Unknown Source) at
> j.u.c.CompletableFuture.postFire(Unknown Source) at
> j.u.c.CompletableFuture$UniWhenComplete.tryFire(Unknown Source) at
> j.u.c.CompletableFuture$Completion.exec(Unknown Source) at
> j.u.c.ForkJoinTask.doExec(Unknown Source) at
> j.u.c.ForkJoinPool$WorkQueue.topLevelExec(Unknown Source) at
> j.u.c.ForkJoinPool.scan(Unknown Source) at
> j.u.c.ForkJoinPool.runWorker(Unknown Source) at
> j.u.c.ForkJoinWorkerThread.run(Unknown Source){code}
>
> {color:#00}When logging the result http code and body{color}
>
> {code:java}
> LOG.error("error while joining LRA: {} / {}", response.statusCode(),
> response.body());{code}
> {color:#00}i am getting this:{color}
> {code:java}
> error while joining LRA: 400 / error: URL is double encoded{code}
> {color:#00}The problem can be solved by not url encoding the given urls
> within the joinLRA payload.{color}
>
> org.apache.camel.service.lra.LRAUrlBuilder -> query:
>
> This code should not be executed:
>
> {code:java}
> key = URLEncoder.encode(toNonnullString(key), StandardCharsets.UTF_8.name());
> value = URLEncoder.encode(toNonnullString(value),
> StandardCharsets.UTF_8.name());
> {code}
>
> {color:#0451a5}2){color}{color:#00} Decode given query parameter from
> Oracle LRA-Coordinator call{color}
> {color:#00}After solving 1), i am getting a new exception:{color}
> {code:java}
> j.l.IllegalArgumentException: URI direct%3A%2F%2Fsaga1_sagaService_complete
> is not allowed at
> o.a.c.s.l.LRASagaRoutes.verifyRequest(LRASagaRoutes.java:107) at
> o.a.c.s.p.DelegateS
[jira] [Resolved] (CAMEL-21229) camel-spring-boot - Upgrade to 3.3.4
[ https://issues.apache.org/jira/browse/CAMEL-21229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-21229. - Resolution: Fixed > camel-spring-boot - Upgrade to 3.3.4 > > > Key: CAMEL-21229 > URL: https://issues.apache.org/jira/browse/CAMEL-21229 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.8.1, 4.9.0 > > > To be released later this week -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-21229) camel-spring-boot - Upgrade to 3.3.4
[ https://issues.apache.org/jira/browse/CAMEL-21229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-21229: --- Assignee: Claus Ibsen > camel-spring-boot - Upgrade to 3.3.4 > > > Key: CAMEL-21229 > URL: https://issues.apache.org/jira/browse/CAMEL-21229 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.8.1, 4.9.0 > > > To be released later this week -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21243) camel-braintree-starter tries to use org.osgi:org.osgi.core:8.0.0
[
https://issues.apache.org/jira/browse/CAMEL-21243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21243:
Fix Version/s: 4.8.1
4.9.0
> camel-braintree-starter tries to use org.osgi:org.osgi.core:8.0.0
> -
>
> Key: CAMEL-21243
> URL: https://issues.apache.org/jira/browse/CAMEL-21243
> Project: Camel
> Issue Type: Bug
> Components: camel-braintree, camel-spring-boot
>Reporter: Thomas Cunningham
>Priority: Major
> Fix For: 4.8.1, 4.9.0
>
>
> I get the following error trying to build camel-braintree-starter
> {code:java}
> [INFO] < org.apache.camel.springboot:camel-braintree-starter
> >-
> [INFO] Building Camel SB Starters :: Braintree 4.9.0-SNAPSHOT
> [INFO] from pom.xml
> [INFO] [ jar
> ]-
> [WARNING] The POM for org.osgi:org.osgi.core:jar:8.0.0 is missing, no
> dependency information available
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.492 s
> [INFO] Finished at: 2024-09-19T07:48:51-04:00
> [INFO]
>
> [ERROR] Failed to execute goal on project camel-braintree-starter: Could not
> resolve dependencies for project
> org.apache.camel.springboot:camel-braintree-starter:jar:4.9.0-SNAPSHOT
> [ERROR] dependency: org.osgi:org.osgi.core:jar:8.0.0 (compile)
> [ERROR] org.osgi:org.osgi.core:jar:8.0.0 was not found in
> http://10.0.144.111:8081/repository/maven-public/ during a previous attempt.
> This failure was cached in the local repository and resolution is not
> reattempted until the update interval of fuse-repository has elapsed or
> updates are forced
> [ERROR]{code}
> It looks like org.osgi:org.osgi.core:8.0.0 does not exist - the last version
> was 6.0.0, and then it was renamed to org.osgi:osgi.core -
> [https://mvnrepository.com/artifact/org.osgi/osgi.core]
>
> com.braintreepayments.gateway:braintree-java:3.35.0 uses
> org.osgi:org.osgi.core:4.2.0
> [https://repo1.maven.org/maven2/com/braintreepayments/gateway/braintree-java/3.35.0/braintree-java-3.35.0.pom]
> but my guess is something wrong with the manifest settings? I'd like to
> add a dependencyManagement entry to force use of org.osgi:org.osgi.core:4.2.0
> so that camel-braintree-starter compiles.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21243) camel-braintree-starter tries to use org.osgi:org.osgi.core:8.0.0
[
https://issues.apache.org/jira/browse/CAMEL-21243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21243:
Affects Version/s: 4.8.0
> camel-braintree-starter tries to use org.osgi:org.osgi.core:8.0.0
> -
>
> Key: CAMEL-21243
> URL: https://issues.apache.org/jira/browse/CAMEL-21243
> Project: Camel
> Issue Type: Bug
> Components: camel-braintree, camel-spring-boot
>Affects Versions: 4.8.0
>Reporter: Thomas Cunningham
>Priority: Major
> Fix For: 4.8.1, 4.9.0
>
>
> I get the following error trying to build camel-braintree-starter
> {code:java}
> [INFO] < org.apache.camel.springboot:camel-braintree-starter
> >-
> [INFO] Building Camel SB Starters :: Braintree 4.9.0-SNAPSHOT
> [INFO] from pom.xml
> [INFO] [ jar
> ]-
> [WARNING] The POM for org.osgi:org.osgi.core:jar:8.0.0 is missing, no
> dependency information available
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.492 s
> [INFO] Finished at: 2024-09-19T07:48:51-04:00
> [INFO]
>
> [ERROR] Failed to execute goal on project camel-braintree-starter: Could not
> resolve dependencies for project
> org.apache.camel.springboot:camel-braintree-starter:jar:4.9.0-SNAPSHOT
> [ERROR] dependency: org.osgi:org.osgi.core:jar:8.0.0 (compile)
> [ERROR] org.osgi:org.osgi.core:jar:8.0.0 was not found in
> http://10.0.144.111:8081/repository/maven-public/ during a previous attempt.
> This failure was cached in the local repository and resolution is not
> reattempted until the update interval of fuse-repository has elapsed or
> updates are forced
> [ERROR]{code}
> It looks like org.osgi:org.osgi.core:8.0.0 does not exist - the last version
> was 6.0.0, and then it was renamed to org.osgi:osgi.core -
> [https://mvnrepository.com/artifact/org.osgi/osgi.core]
>
> com.braintreepayments.gateway:braintree-java:3.35.0 uses
> org.osgi:org.osgi.core:4.2.0
> [https://repo1.maven.org/maven2/com/braintreepayments/gateway/braintree-java/3.35.0/braintree-java-3.35.0.pom]
> but my guess is something wrong with the manifest settings? I'd like to
> add a dependencyManagement entry to force use of org.osgi:org.osgi.core:4.2.0
> so that camel-braintree-starter compiles.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21243) camel-braintree-starter tries to use org.osgi:org.osgi.core:8.0.0
[
https://issues.apache.org/jira/browse/CAMEL-21243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883083#comment-17883083
]
Claus Ibsen commented on CAMEL-21243:
-
Can you backport this to 4.8.x branch
> camel-braintree-starter tries to use org.osgi:org.osgi.core:8.0.0
> -
>
> Key: CAMEL-21243
> URL: https://issues.apache.org/jira/browse/CAMEL-21243
> Project: Camel
> Issue Type: Bug
> Components: camel-braintree, camel-spring-boot
>Affects Versions: 4.8.0
>Reporter: Thomas Cunningham
>Priority: Major
> Fix For: 4.8.1, 4.9.0
>
>
> I get the following error trying to build camel-braintree-starter
> {code:java}
> [INFO] < org.apache.camel.springboot:camel-braintree-starter
> >-
> [INFO] Building Camel SB Starters :: Braintree 4.9.0-SNAPSHOT
> [INFO] from pom.xml
> [INFO] [ jar
> ]-
> [WARNING] The POM for org.osgi:org.osgi.core:jar:8.0.0 is missing, no
> dependency information available
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.492 s
> [INFO] Finished at: 2024-09-19T07:48:51-04:00
> [INFO]
>
> [ERROR] Failed to execute goal on project camel-braintree-starter: Could not
> resolve dependencies for project
> org.apache.camel.springboot:camel-braintree-starter:jar:4.9.0-SNAPSHOT
> [ERROR] dependency: org.osgi:org.osgi.core:jar:8.0.0 (compile)
> [ERROR] org.osgi:org.osgi.core:jar:8.0.0 was not found in
> http://10.0.144.111:8081/repository/maven-public/ during a previous attempt.
> This failure was cached in the local repository and resolution is not
> reattempted until the update interval of fuse-repository has elapsed or
> updates are forced
> [ERROR]{code}
> It looks like org.osgi:org.osgi.core:8.0.0 does not exist - the last version
> was 6.0.0, and then it was renamed to org.osgi:osgi.core -
> [https://mvnrepository.com/artifact/org.osgi/osgi.core]
>
> com.braintreepayments.gateway:braintree-java:3.35.0 uses
> org.osgi:org.osgi.core:4.2.0
> [https://repo1.maven.org/maven2/com/braintreepayments/gateway/braintree-java/3.35.0/braintree-java-3.35.0.pom]
> but my guess is something wrong with the manifest settings? I'd like to
> add a dependencyManagement entry to force use of org.osgi:org.osgi.core:4.2.0
> so that camel-braintree-starter compiles.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21242) camel-jolokia-starter - a new starter to easily expose Jolokia endpoint
[ https://issues.apache.org/jira/browse/CAMEL-21242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21242: Component/s: camel-spring-boot > camel-jolokia-starter - a new starter to easily expose Jolokia endpoint > > > Key: CAMEL-21242 > URL: https://issues.apache.org/jira/browse/CAMEL-21242 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Reporter: Marco Carletti >Assignee: Marco Carletti >Priority: Major > Fix For: 4.9.0 > > > In order to monitor Camel on Spring Boot applications it would be useful to > have a configurable starter that make the configuration easy and to allow a > Jolokia agentless solution, based on existing [Support for Jolokia in Spring > Boot|https://jolokia.org/reference/html/manual/spring.html] > This library already exposes (optionally) the Jolokia endpoint using Spring > Boot Actuator, but it would be more configurable having a separated endpoint > dedicated to Jolokia, completely separated from actuator and running on > separated thread(s) according to Jolokia server specifications. > Moreover it prepares a basic setup on Kubernetes platform -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21242) camel-jolokia-starter - a new starter to easily expose Jolokia endpoint
[ https://issues.apache.org/jira/browse/CAMEL-21242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21242: Fix Version/s: 4.9.0 > camel-jolokia-starter - a new starter to easily expose Jolokia endpoint > > > Key: CAMEL-21242 > URL: https://issues.apache.org/jira/browse/CAMEL-21242 > Project: Camel > Issue Type: New Feature >Reporter: Marco Carletti >Assignee: Marco Carletti >Priority: Major > Fix For: 4.9.0 > > > In order to monitor Camel on Spring Boot applications it would be useful to > have a configurable starter that make the configuration easy and to allow a > Jolokia agentless solution, based on existing [Support for Jolokia in Spring > Boot|https://jolokia.org/reference/html/manual/spring.html] > This library already exposes (optionally) the Jolokia endpoint using Spring > Boot Actuator, but it would be more configurable having a separated endpoint > dedicated to Jolokia, completely separated from actuator and running on > separated thread(s) according to Jolokia server specifications. > Moreover it prepares a basic setup on Kubernetes platform -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21241) camel-core - Properties dev console to capture actual values
[ https://issues.apache.org/jira/browse/CAMEL-21241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-21241. - Resolution: Fixed > camel-core - Properties dev console to capture actual values > > > Key: CAMEL-21241 > URL: https://issues.apache.org/jira/browse/CAMEL-21241 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.9.0 > > > When you use property placeholders with ENV, or other functions then you > would like to know the actual value, and be able to show that in dev console. > We should capture this details. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21241) camel-core - Properties dev console to capture actual values
[ https://issues.apache.org/jira/browse/CAMEL-21241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882964#comment-17882964 ] Claus Ibsen edited comment on CAMEL-21241 at 9/19/24 1:55 PM: -- TODO: properties component *DONE* TODO: dev console *DONE* TODO: jbang command *DONE* TODO: nested values vs original value *DONE* TODO: properties function as source so you know that the value is from configmap / security vault etc. *DONE* was (Author: davsclaus): TODO: properties component *DONE* TODO: dev console *DONE* TODO: jbang command TODO: nested values vs original value *DONE* TODO: properties function as source so you know that the value is from configmap / security vault etc. *DONE* > camel-core - Properties dev console to capture actual values > > > Key: CAMEL-21241 > URL: https://issues.apache.org/jira/browse/CAMEL-21241 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.9.0 > > > When you use property placeholders with ENV, or other functions then you > would like to know the actual value, and be able to show that in dev console. > We should capture this details. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21238) camel-jbang - k8s run - Reloading project does not change route behaviour
[
https://issues.apache.org/jira/browse/CAMEL-21238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883000#comment-17883000
]
Claus Ibsen edited comment on CAMEL-21238 at 9/19/24 1:34 PM:
--
I fixed a few issues with re-export that prevented re-deploy. Now, re-deploy
starts, but there is an issue with the shutdown hook and re-capturing the
output of the new k8s process. Currently (as you say), there is no in-container
hot swap of camel resources in a running container (as we had in camel-k) and
given all complexities and even the questionable idea of swapping stuff in an
otherwise immutable container, I'd prefer the cleaner route of re-export +
re-deploy.
>From the usage perspective, it is ...
ctrl+c
camel k8s run ...
stopping the container already removes the k8s resources (because --dev cleanup)
camel k8s run, is the re-export + re-deploy
yes, I really think that there is little benefit and lots of potential headache
with hot swapping resources (i.e. what if I want to change two files)
was (Author: tdiesler):
I fixed a few issues with re-export that prevented re-deploy. Now, re-deploy
starts, but there is an issue with the shutdown hook and re-capturing the
output of the new k8s process. Currently (as you say), there is no in-container
hot swap of camel resources in a running container (as we had in camel-k) and
given all complexities and even the questionable idea of swapping stuff in an
otherwise immutable container, I'd prefer the cleaner route of re-export +
re-deploy.
>From the usage perspective, it is ...
ctrl+c
camel k8s run ...
stopping the container already removes the k8s resources (because --dev cleanup)
camel k8s run, is the re-export + re-deploy
yes, I really think that there is little benefit and lots of potential headache
with hot swapping resources (i.e. what if I want to change two files)
https://redhat-internal.slack.com/archives/C06D1DXF0KU/p1726747303525909
> camel-jbang - k8s run - Reloading project does not change route behaviour
> -
>
> Key: CAMEL-21238
> URL: https://issues.apache.org/jira/browse/CAMEL-21238
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 4.9.0
>
>
> When running a project with `--dev` like this ...
> {code}
> jbang camel kubernetes run timer-log-route.yaml --logs --dev \
> --gav=examples:timer-log:1.0.0 \
> --trait container.imagePullPolicy=IfNotPresent \
> --trait service.type=NodePort \
> --runtime=quarkus
> {code}
> I see ...
> {code}
> Reloading project due to file change: timer-log-route.yaml
> {code}
> without image re-build/deploy
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21241) camel-core - Properties dev console to capture actual values
[ https://issues.apache.org/jira/browse/CAMEL-21241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882964#comment-17882964 ] Claus Ibsen edited comment on CAMEL-21241 at 9/19/24 1:32 PM: -- TODO: properties component *DONE* TODO: dev console *DONE* TODO: jbang command TODO: nested values vs original value *DONE* TODO: properties function as source so you know that the value is from configmap / security vault etc. *DONE* was (Author: davsclaus): TODO: properties component *DONE* TODO: dev console *DONE* TODO: jbang command TODO: nested values vs original value *DONE* TODO: properties function as source so you know that the value is from configmap / security vault etc. > camel-core - Properties dev console to capture actual values > > > Key: CAMEL-21241 > URL: https://issues.apache.org/jira/browse/CAMEL-21241 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.9.0 > > > When you use property placeholders with ENV, or other functions then you > would like to know the actual value, and be able to show that in dev console. > We should capture this details. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21241) camel-core - Properties dev console to capture actual values
[ https://issues.apache.org/jira/browse/CAMEL-21241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882964#comment-17882964 ] Claus Ibsen edited comment on CAMEL-21241 at 9/19/24 1:23 PM: -- TODO: properties component *DONE* TODO: dev console *DONE* TODO: jbang command TODO: nested values vs original value *DONE* TODO: properties function as source so you know that the value is from configmap / security vault etc. was (Author: davsclaus): TODO: properties component *DONE* TODO: dev console *DONE* TODO: jbang command TODO: nested values vs original value > camel-core - Properties dev console to capture actual values > > > Key: CAMEL-21241 > URL: https://issues.apache.org/jira/browse/CAMEL-21241 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.9.0 > > > When you use property placeholders with ENV, or other functions then you > would like to know the actual value, and be able to show that in dev console. > We should capture this details. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21241) camel-core - Properties dev console to capture actual values
[ https://issues.apache.org/jira/browse/CAMEL-21241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882964#comment-17882964 ] Claus Ibsen edited comment on CAMEL-21241 at 9/19/24 12:20 PM: --- TODO: properties component *DONE* TODO: dev console *DONE* TODO: jbang command TODO: nested values vs original value was (Author: davsclaus): TODO: properties component *DONE* TODO: dev console *DONE* TODO: jbang command > camel-core - Properties dev console to capture actual values > > > Key: CAMEL-21241 > URL: https://issues.apache.org/jira/browse/CAMEL-21241 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.9.0 > > > When you use property placeholders with ENV, or other functions then you > would like to know the actual value, and be able to show that in dev console. > We should capture this details. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21238) camel-jbang - k8s run - Reloading project does not change route behaviour
[
https://issues.apache.org/jira/browse/CAMEL-21238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882997#comment-17882997
]
Claus Ibsen commented on CAMEL-21238:
-
Thanks.
Yes I see benefit - its similar to Camel K, for folks that wants to quickly run
directly inside k8s via the CLI and be able to edit a few files locally.
The other mode can be explored later (create a Jira ticket for that).
> camel-jbang - k8s run - Reloading project does not change route behaviour
> -
>
> Key: CAMEL-21238
> URL: https://issues.apache.org/jira/browse/CAMEL-21238
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 4.9.0
>
>
> When running a project with `--dev` like this ...
> {code}
> jbang camel kubernetes run timer-log-route.yaml --logs --dev \
> --gav=examples:timer-log:1.0.0 \
> --trait container.imagePullPolicy=IfNotPresent \
> --trait service.type=NodePort \
> --runtime=quarkus
> {code}
> I see ...
> {code}
> Reloading project due to file change: timer-log-route.yaml
> {code}
> without image re-build/deploy
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21238) camel-jbang - k8s run - Reloading project does not change route behaviour
[
https://issues.apache.org/jira/browse/CAMEL-21238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882982#comment-17882982
]
Claus Ibsen commented on CAMEL-21238:
-
[~christophd] did most of this command - so it may be good to get his
perspective
> camel-jbang - k8s run - Reloading project does not change route behaviour
> -
>
> Key: CAMEL-21238
> URL: https://issues.apache.org/jira/browse/CAMEL-21238
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 4.9.0
>
>
> When running a project with `--dev` like this ...
> {code}
> jbang camel kubernetes run timer-log-route.yaml --logs --dev \
> --gav=examples:timer-log:1.0.0 \
> --trait container.imagePullPolicy=IfNotPresent \
> --trait service.type=NodePort \
> --runtime=quarkus
> {code}
> I see ...
> {code}
> Reloading project due to file change: timer-log-route.yaml
> {code}
> without image re-build/deploy
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21241) camel-core - Properties dev console to capture actual values
[ https://issues.apache.org/jira/browse/CAMEL-21241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882964#comment-17882964 ] Claus Ibsen edited comment on CAMEL-21241 at 9/19/24 10:59 AM: --- TODO: properties component *DONE* TODO: dev console *DONE* TODO: jbang command was (Author: davsclaus): TODO: properties component *DONE* TODO: JMX TODO: dev console TODO: jbang command > camel-core - Properties dev console to capture actual values > > > Key: CAMEL-21241 > URL: https://issues.apache.org/jira/browse/CAMEL-21241 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.9.0 > > > When you use property placeholders with ENV, or other functions then you > would like to know the actual value, and be able to show that in dev console. > We should capture this details. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21241) camel-core - Properties dev console to capture actual values
[ https://issues.apache.org/jira/browse/CAMEL-21241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882964#comment-17882964 ] Claus Ibsen commented on CAMEL-21241: - TODO: properties component *DONE* TODO: JMX TODO: dev console TODO: jbang command > camel-core - Properties dev console to capture actual values > > > Key: CAMEL-21241 > URL: https://issues.apache.org/jira/browse/CAMEL-21241 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.9.0 > > > When you use property placeholders with ENV, or other functions then you > would like to know the actual value, and be able to show that in dev console. > We should capture this details. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-21241) camel-core - Properties dev console to capture actual values
[ https://issues.apache.org/jira/browse/CAMEL-21241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-21241: --- Assignee: Claus Ibsen > camel-core - Properties dev console to capture actual values > > > Key: CAMEL-21241 > URL: https://issues.apache.org/jira/browse/CAMEL-21241 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.9.0 > > > When you use property placeholders with ENV, or other functions then you > would like to know the actual value, and be able to show that in dev console. > We should capture this details. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21241) camel-core - Properties dev console to capture actual values
[ https://issues.apache.org/jira/browse/CAMEL-21241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21241: Priority: Minor (was: Major) > camel-core - Properties dev console to capture actual values > > > Key: CAMEL-21241 > URL: https://issues.apache.org/jira/browse/CAMEL-21241 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.9.0 > > > When you use property placeholders with ENV, or other functions then you > would like to know the actual value, and be able to show that in dev console. > We should capture this details. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21197) URISupport.parseQuery is not decoding correctly
[
https://issues.apache.org/jira/browse/CAMEL-21197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882933#comment-17882933
]
Claus Ibsen commented on CAMEL-21197:
-
Camel has its own code for parsing its endpoints that resemble URIs and have
various optimized code for this.
This code is NOT intended as general purpose URI utils for any end users or
whatever they do. Its for working with Camel.
The issue was an Oracle TX manager that has some issue - focus on fixing it
there.
Camel v5 has a goal of changing this URI endpoint parsing inside Camel (there
is a Jira ticket somewhere).
> URISupport.parseQuery is not decoding correctly
> ---
>
> Key: CAMEL-21197
> URL: https://issues.apache.org/jira/browse/CAMEL-21197
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.7.0
>Reporter: Dirk Fiedler
>Priority: Minor
>
> {color:#00}Hi team,{color}
> {color:#00}while using *URISupport.parseQuery* the given query was not
> correctly decoded:{color}
> *{color:#00}Sample JUnit test
> (org.apache.camel.util.URISupportTest):{color}*
>
> {code:java}
> @Test
> public void testParseQueryDFi() throws Exception {
> Map map =
> URISupport.parseQuery("Camel-Saga-Complete=direct%3A%2F%2Fsaga1_sagaService_complete");
> assertEquals(1, map.size());
> assertEquals("direct://saga1_sagaService_complete",
> map.get("Camel-Saga-Complete"));
> } {code}
> {color:#00}If i handover the query
> 'Camel-Saga-Complete=direct%3A%2F%2Fsaga1_sagaService_complete'
> i expect the decoded value {color}{color:#00}for 'Camel-Saga-Complete' as
> 'direct://saga1_sagaService_complete'.{color}
> {color:#00}I am wrong? Did i understand the utility class wrong?{color}
> {color:#00}Within the code i can see, that the string was adjusted to
> replace '%', this is {color}
> {color:#00}causing the issue:{color}
> *{color:#00}URIScanner.addParameter:{color}*
>
> {code:java}
> if (isRaw) {
> text = value.toString();
> } else {
> // need to replace % with %25 to avoid losing "%" when decoding
> final String s = replacePercent(value.toString());
> text = URLDecoder.decode(s, CHARSET);
> }{code}
>
> {color:#00}best regards{color}
> {color:#00}Dirk{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-21241) camel-core - Properties dev console to capture actual values
Claus Ibsen created CAMEL-21241: --- Summary: camel-core - Properties dev console to capture actual values Key: CAMEL-21241 URL: https://issues.apache.org/jira/browse/CAMEL-21241 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Fix For: 4.9.0 When you use property placeholders with ENV, or other functions then you would like to know the actual value, and be able to show that in dev console. We should capture this details. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21240) camel-jbang - Download does not work with --source-dir option
[ https://issues.apache.org/jira/browse/CAMEL-21240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-21240. - Resolution: Fixed > camel-jbang - Download does not work with --source-dir option > - > > Key: CAMEL-21240 > URL: https://issues.apache.org/jira/browse/CAMEL-21240 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Affects Versions: 4.8.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.8.1, 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21240) camel-jbang - Download does not work with --source-dir option
Claus Ibsen created CAMEL-21240: --- Summary: camel-jbang - Download does not work with --source-dir option Key: CAMEL-21240 URL: https://issues.apache.org/jira/browse/CAMEL-21240 Project: Camel Issue Type: Bug Components: camel-jbang Affects Versions: 4.8.0 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 4.8.1, 4.9.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21085) camel-jbang - Init - Support providing absolute path for camel file creation using Camel JBang
[
https://issues.apache.org/jira/browse/CAMEL-21085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-21085.
-
Resolution: Fixed
> camel-jbang - Init - Support providing absolute path for camel file creation
> using Camel JBang
> --
>
> Key: CAMEL-21085
> URL: https://issues.apache.org/jira/browse/CAMEL-21085
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
>Affects Versions: 4.7.0
>Reporter: Aurélien Pupier
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.9.0
>
>
> currently it is failing with this kind of error:
> {noformat}
> (base) apupier@localhost:~/ws/record-gif-readme$ jbang
> '-Dcamel.jbang.version=4.7.0' camel@apache/camel init
> /home/apupier/ws/record-gif-readme/target-folder/anothersecondone.camel.yaml
> java.io.FileNotFoundException:
> ./home/apupier/ws/record-gif-readme/target-folder/anothersecondone.camel.yaml
> (No such file or directory)
> at java.base/java.io.FileOutputStream.open0(Native Method)
> at java.base/java.io.FileOutputStream.open(FileOutputStream.java:289)
> at
> java.base/java.io.FileOutputStream.(FileOutputStream.java:230)
> at
> org.apache.camel.dsl.jbang.core.commands.Init.execute(Init.java:174)
> at org.apache.camel.dsl.jbang.core.commands.Init.doCall(Init.java:82)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
> at picocli.CommandLine.executeUserObject(CommandLine.java:2045)
> at picocli.CommandLine.access$1500(CommandLine.java:148)
> at
> picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)
> at
> picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
> at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
> at picocli.CommandLine.execute(CommandLine.java:2174)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:168)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:61)
> at main.CamelJBang.main(CamelJBang.java:36)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21085) camel-jbang - Init - Support providing absolute path for camel file creation using Camel JBang
[
https://issues.apache.org/jira/browse/CAMEL-21085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882732#comment-17882732
]
Claus Ibsen commented on CAMEL-21085:
-
You should really use --dir for the folder, and the file should just be the
file name.
> camel-jbang - Init - Support providing absolute path for camel file creation
> using Camel JBang
> --
>
> Key: CAMEL-21085
> URL: https://issues.apache.org/jira/browse/CAMEL-21085
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
>Affects Versions: 4.7.0
>Reporter: Aurélien Pupier
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.9.0
>
>
> currently it is failing with this kind of error:
> {noformat}
> (base) apupier@localhost:~/ws/record-gif-readme$ jbang
> '-Dcamel.jbang.version=4.7.0' camel@apache/camel init
> /home/apupier/ws/record-gif-readme/target-folder/anothersecondone.camel.yaml
> java.io.FileNotFoundException:
> ./home/apupier/ws/record-gif-readme/target-folder/anothersecondone.camel.yaml
> (No such file or directory)
> at java.base/java.io.FileOutputStream.open0(Native Method)
> at java.base/java.io.FileOutputStream.open(FileOutputStream.java:289)
> at
> java.base/java.io.FileOutputStream.(FileOutputStream.java:230)
> at
> org.apache.camel.dsl.jbang.core.commands.Init.execute(Init.java:174)
> at org.apache.camel.dsl.jbang.core.commands.Init.doCall(Init.java:82)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
> at picocli.CommandLine.executeUserObject(CommandLine.java:2045)
> at picocli.CommandLine.access$1500(CommandLine.java:148)
> at
> picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)
> at
> picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
> at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
> at picocli.CommandLine.execute(CommandLine.java:2174)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:168)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:61)
> at main.CamelJBang.main(CamelJBang.java:36)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21239) camel-report-maven-plugin - NPE if route does not have id
[ https://issues.apache.org/jira/browse/CAMEL-21239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882731#comment-17882731 ] Claus Ibsen commented on CAMEL-21239: - Yes you must have IDs now > camel-report-maven-plugin - NPE if route does not have id > - > > Key: CAMEL-21239 > URL: https://issues.apache.org/jira/browse/CAMEL-21239 > Project: Camel > Issue Type: Bug > Components: tooling >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.4.4, 4.8.1, 4.9.0 > > > Caused by: java.lang.NullPointerException: Cannot invoke > "org.w3c.dom.Node.getNodeValue()" because the return value of > "org.w3c.dom.NamedNodeMap.getNamedItem(String)" is null > at > org.apache.camel.parser.helper.RouteCoverageHelper.parseDumpRouteCoverageByRouteId > (RouteCoverageHelper.java:70) > at org.apache.camel.maven.RouteCoverageMojo.grabDumpData > (RouteCoverageMojo.java:263) > at org.apache.camel.maven.RouteCoverageMojo.execute > (RouteCoverageMojo.java:228) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:126) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21199) Camel-jackson not properly marshalling 4-byte characters
[
https://issues.apache.org/jira/browse/CAMEL-21199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882723#comment-17882723
]
Claus Ibsen commented on CAMEL-21199:
-
Thanks for getting this into jackson itself (best place).
It will take a while as we need Spring Boot and Quarkus to also upgrade to
jackson 2.18.x
> Camel-jackson not properly marshalling 4-byte characters
>
>
> Key: CAMEL-21199
> URL: https://issues.apache.org/jira/browse/CAMEL-21199
> Project: Camel
> Issue Type: Bug
> Components: camel-jackson
>Reporter: Radovan Netuka
>Assignee: Radovan Netuka
>Priority: Major
> Fix For: 4.9.0
>
>
> Camel-jackson doesn't handle 4-byte characters well. Marshalling a 4-byte
> Japanese kanji character results in two UTF-16 escapes to be written instead
> of the character itself. While this is ok for emoji an such, it's not for
> natural languages.
> Jackson issue:
> [FasterXML/jackson-core#223|https://github.com/FasterXML/jackson-core/issues/223]
>
> Reproducer:
> {code:java}
> from("file:data?file-name=input.txt&noop=true")
> .log("${body}")
> .unmarshal().json(JsonLibrary.Jackson)
> .log("${body[0]['name']}")
> .marshal().json(JsonLibrary.Jackson, true)
> .log("${body}"); {code}
>
> with the file input.txt containing:
> {code:java}
> [{"name": "システム𩸽"}] {code}
>
> Expected output seen in the log: *"システム𩸽"*
> Actual output seen in the log: *"システム\uD867\uDE3D"*
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20883) Remove addPluginArtifactMetadata mojo usage
[ https://issues.apache.org/jira/browse/CAMEL-20883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882719#comment-17882719 ] Claus Ibsen commented on CAMEL-20883: - It may be the bom-generator-maven-plugin and camel-package-maven-plugin plugins that are from Camel itself, may need some code updates / dependency cleanup etc. > Remove addPluginArtifactMetadata mojo usage > --- > > Key: CAMEL-20883 > URL: https://issues.apache.org/jira/browse/CAMEL-20883 > Project: Camel > Issue Type: Task > Components: build system >Reporter: Aurélien Pupier >Priority: Minor > Fix For: 4.9.0 > > > in log there is 14 times: > ``` > 14:00:33,645 [INFO] --- plugin:3.13.1:addPluginArtifactMetadata > (default-addPluginArtifactMetadata) @ camel-package-maven-plugin --- > 14:00:33,645 [INFO] This Mojo is not used in Maven version 3.9.0 and above > ``` > > In this case I think we need to upgrade the minimal Maven version (currently > at 3.5.0): > [https://github.com/apache/camel/blob/07c502761c4d450f5b2b7bba19ce4f69f507212d/pom.xml#L915] > > Is it fine to upgrade the minimal Maven version to 3.9.0? > I guess we are testing anyway only with the version which is defined by the > Maven wrapper? > Advantages: > * less message in the log > * small time gain on the build > * less code to maintain > Drawback: > - forcing all developers to use recent Maven (which might also be seen as an > advantage :) ) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20883) Remove addPluginArtifactMetadata mojo usage
[ https://issues.apache.org/jira/browse/CAMEL-20883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882716#comment-17882716 ] Claus Ibsen commented on CAMEL-20883: - I still see [INFO] --- plugin:3.15.0:addPluginArtifactMetadata (default-addPluginArtifactMetadata) @ bom-generator-maven-plugin --- [INFO] This Mojo is not used in Maven version 3.9.0 and above > Remove addPluginArtifactMetadata mojo usage > --- > > Key: CAMEL-20883 > URL: https://issues.apache.org/jira/browse/CAMEL-20883 > Project: Camel > Issue Type: Task > Components: build system >Reporter: Aurélien Pupier >Priority: Minor > Fix For: 4.9.0 > > > in log there is 14 times: > ``` > 14:00:33,645 [INFO] --- plugin:3.13.1:addPluginArtifactMetadata > (default-addPluginArtifactMetadata) @ camel-package-maven-plugin --- > 14:00:33,645 [INFO] This Mojo is not used in Maven version 3.9.0 and above > ``` > > In this case I think we need to upgrade the minimal Maven version (currently > at 3.5.0): > [https://github.com/apache/camel/blob/07c502761c4d450f5b2b7bba19ce4f69f507212d/pom.xml#L915] > > Is it fine to upgrade the minimal Maven version to 3.9.0? > I guess we are testing anyway only with the version which is defined by the > Maven wrapper? > Advantages: > * less message in the log > * small time gain on the build > * less code to maintain > Drawback: > - forcing all developers to use recent Maven (which might also be seen as an > advantage :) ) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21239) camel-report-maven-plugin - NPE if route does not have id
[ https://issues.apache.org/jira/browse/CAMEL-21239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-21239. - Resolution: Fixed > camel-report-maven-plugin - NPE if route does not have id > - > > Key: CAMEL-21239 > URL: https://issues.apache.org/jira/browse/CAMEL-21239 > Project: Camel > Issue Type: Bug > Components: tooling >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.4.4, 4.8.1, 4.9.0 > > > Caused by: java.lang.NullPointerException: Cannot invoke > "org.w3c.dom.Node.getNodeValue()" because the return value of > "org.w3c.dom.NamedNodeMap.getNamedItem(String)" is null > at > org.apache.camel.parser.helper.RouteCoverageHelper.parseDumpRouteCoverageByRouteId > (RouteCoverageHelper.java:70) > at org.apache.camel.maven.RouteCoverageMojo.grabDumpData > (RouteCoverageMojo.java:263) > at org.apache.camel.maven.RouteCoverageMojo.execute > (RouteCoverageMojo.java:228) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:126) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-21239) camel-report-maven-plugin - NPE if route does not have id
[ https://issues.apache.org/jira/browse/CAMEL-21239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-21239: --- Assignee: Claus Ibsen > camel-report-maven-plugin - NPE if route does not have id > - > > Key: CAMEL-21239 > URL: https://issues.apache.org/jira/browse/CAMEL-21239 > Project: Camel > Issue Type: Bug > Components: tooling >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.4.4, 4.8.1, 4.9.0 > > > Caused by: java.lang.NullPointerException: Cannot invoke > "org.w3c.dom.Node.getNodeValue()" because the return value of > "org.w3c.dom.NamedNodeMap.getNamedItem(String)" is null > at > org.apache.camel.parser.helper.RouteCoverageHelper.parseDumpRouteCoverageByRouteId > (RouteCoverageHelper.java:70) > at org.apache.camel.maven.RouteCoverageMojo.grabDumpData > (RouteCoverageMojo.java:263) > at org.apache.camel.maven.RouteCoverageMojo.execute > (RouteCoverageMojo.java:228) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:126) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21239) camel-report-maven-plugin - NPE if route does not have id
Claus Ibsen created CAMEL-21239: --- Summary: camel-report-maven-plugin - NPE if route does not have id Key: CAMEL-21239 URL: https://issues.apache.org/jira/browse/CAMEL-21239 Project: Camel Issue Type: Bug Components: tooling Reporter: Claus Ibsen Fix For: 4.4.4, 4.8.1, 4.9.0 Caused by: java.lang.NullPointerException: Cannot invoke "org.w3c.dom.Node.getNodeValue()" because the return value of "org.w3c.dom.NamedNodeMap.getNamedItem(String)" is null at org.apache.camel.parser.helper.RouteCoverageHelper.parseDumpRouteCoverageByRouteId (RouteCoverageHelper.java:70) at org.apache.camel.maven.RouteCoverageMojo.grabDumpData (RouteCoverageMojo.java:263) at org.apache.camel.maven.RouteCoverageMojo.execute (RouteCoverageMojo.java:228) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:126) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20858) Provide message log on files transformed with Camel JBang
[ https://issues.apache.org/jira/browse/CAMEL-20858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882713#comment-17882713 ] Claus Ibsen commented on CAMEL-20858: - We should look at printing more activity in the jbang commands when --verbose is enabled > Provide message log on files transformed with Camel JBang > - > > Key: CAMEL-20858 > URL: https://issues.apache.org/jira/browse/CAMEL-20858 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Affects Versions: 4.6.0 >Reporter: Aurélien Pupier >Priority: Minor > Fix For: 4.x > > > When calling transform command, it would be convenient to have a message log > mentioning the file transformed with initial name and final name and if it is > a new file created aor one exists and it is appended -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20883) Remove addPluginArtifactMetadata mojo usage
[ https://issues.apache.org/jira/browse/CAMEL-20883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20883: Fix Version/s: 4.9.0 (was: 4.x) > Remove addPluginArtifactMetadata mojo usage > --- > > Key: CAMEL-20883 > URL: https://issues.apache.org/jira/browse/CAMEL-20883 > Project: Camel > Issue Type: Task > Components: build system >Reporter: Aurélien Pupier >Priority: Minor > Fix For: 4.9.0 > > > in log there is 14 times: > ``` > 14:00:33,645 [INFO] --- plugin:3.13.1:addPluginArtifactMetadata > (default-addPluginArtifactMetadata) @ camel-package-maven-plugin --- > 14:00:33,645 [INFO] This Mojo is not used in Maven version 3.9.0 and above > ``` > > In this case I think we need to upgrade the minimal Maven version (currently > at 3.5.0): > [https://github.com/apache/camel/blob/07c502761c4d450f5b2b7bba19ce4f69f507212d/pom.xml#L915] > > Is it fine to upgrade the minimal Maven version to 3.9.0? > I guess we are testing anyway only with the version which is defined by the > Maven wrapper? > Advantages: > * less message in the log > * small time gain on the build > * less code to maintain > Drawback: > - forcing all developers to use recent Maven (which might also be seen as an > advantage :) ) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21085) camel-jbang - Init - Support providing absolute path for camel file creation using Camel JBang
[
https://issues.apache.org/jira/browse/CAMEL-21085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21085:
Priority: Minor (was: Major)
> camel-jbang - Init - Support providing absolute path for camel file creation
> using Camel JBang
> --
>
> Key: CAMEL-21085
> URL: https://issues.apache.org/jira/browse/CAMEL-21085
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
>Affects Versions: 4.7.0
>Reporter: Aurélien Pupier
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.9.0
>
>
> currently it is failing with this kind of error:
> {noformat}
> (base) apupier@localhost:~/ws/record-gif-readme$ jbang
> '-Dcamel.jbang.version=4.7.0' camel@apache/camel init
> /home/apupier/ws/record-gif-readme/target-folder/anothersecondone.camel.yaml
> java.io.FileNotFoundException:
> ./home/apupier/ws/record-gif-readme/target-folder/anothersecondone.camel.yaml
> (No such file or directory)
> at java.base/java.io.FileOutputStream.open0(Native Method)
> at java.base/java.io.FileOutputStream.open(FileOutputStream.java:289)
> at
> java.base/java.io.FileOutputStream.(FileOutputStream.java:230)
> at
> org.apache.camel.dsl.jbang.core.commands.Init.execute(Init.java:174)
> at org.apache.camel.dsl.jbang.core.commands.Init.doCall(Init.java:82)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
> at picocli.CommandLine.executeUserObject(CommandLine.java:2045)
> at picocli.CommandLine.access$1500(CommandLine.java:148)
> at
> picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)
> at
> picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
> at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
> at picocli.CommandLine.execute(CommandLine.java:2174)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:168)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:61)
> at main.CamelJBang.main(CamelJBang.java:36)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-21085) camel-jbang - Init - Support providing absolute path for camel file creation using Camel JBang
[
https://issues.apache.org/jira/browse/CAMEL-21085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-21085:
---
Assignee: Claus Ibsen
> camel-jbang - Init - Support providing absolute path for camel file creation
> using Camel JBang
> --
>
> Key: CAMEL-21085
> URL: https://issues.apache.org/jira/browse/CAMEL-21085
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
>Affects Versions: 4.7.0
>Reporter: Aurélien Pupier
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.9.0
>
>
> currently it is failing with this kind of error:
> {noformat}
> (base) apupier@localhost:~/ws/record-gif-readme$ jbang
> '-Dcamel.jbang.version=4.7.0' camel@apache/camel init
> /home/apupier/ws/record-gif-readme/target-folder/anothersecondone.camel.yaml
> java.io.FileNotFoundException:
> ./home/apupier/ws/record-gif-readme/target-folder/anothersecondone.camel.yaml
> (No such file or directory)
> at java.base/java.io.FileOutputStream.open0(Native Method)
> at java.base/java.io.FileOutputStream.open(FileOutputStream.java:289)
> at
> java.base/java.io.FileOutputStream.(FileOutputStream.java:230)
> at
> org.apache.camel.dsl.jbang.core.commands.Init.execute(Init.java:174)
> at org.apache.camel.dsl.jbang.core.commands.Init.doCall(Init.java:82)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
> at picocli.CommandLine.executeUserObject(CommandLine.java:2045)
> at picocli.CommandLine.access$1500(CommandLine.java:148)
> at
> picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)
> at
> picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
> at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
> at picocli.CommandLine.execute(CommandLine.java:2174)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:168)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:61)
> at main.CamelJBang.main(CamelJBang.java:36)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21085) camel-jbang - Init - Support providing absolute path for camel file creation using Camel JBang
[
https://issues.apache.org/jira/browse/CAMEL-21085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21085:
Summary: camel-jbang - Init - Support providing absolute path for camel
file creation using Camel JBang (was: Support providing absolute path for
camel file creation using Camel JBang)
> camel-jbang - Init - Support providing absolute path for camel file creation
> using Camel JBang
> --
>
> Key: CAMEL-21085
> URL: https://issues.apache.org/jira/browse/CAMEL-21085
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
>Affects Versions: 4.7.0
>Reporter: Aurélien Pupier
>Priority: Major
> Fix For: 4.9.0
>
>
> currently it is failing with this kind of error:
> {noformat}
> (base) apupier@localhost:~/ws/record-gif-readme$ jbang
> '-Dcamel.jbang.version=4.7.0' camel@apache/camel init
> /home/apupier/ws/record-gif-readme/target-folder/anothersecondone.camel.yaml
> java.io.FileNotFoundException:
> ./home/apupier/ws/record-gif-readme/target-folder/anothersecondone.camel.yaml
> (No such file or directory)
> at java.base/java.io.FileOutputStream.open0(Native Method)
> at java.base/java.io.FileOutputStream.open(FileOutputStream.java:289)
> at
> java.base/java.io.FileOutputStream.(FileOutputStream.java:230)
> at
> org.apache.camel.dsl.jbang.core.commands.Init.execute(Init.java:174)
> at org.apache.camel.dsl.jbang.core.commands.Init.doCall(Init.java:82)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
> at picocli.CommandLine.executeUserObject(CommandLine.java:2045)
> at picocli.CommandLine.access$1500(CommandLine.java:148)
> at
> picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)
> at
> picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
> at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
> at picocli.CommandLine.execute(CommandLine.java:2174)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:168)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:61)
> at main.CamelJBang.main(CamelJBang.java:36)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21085) Support providing absolute path for camel file creation using Camel JBang
[
https://issues.apache.org/jira/browse/CAMEL-21085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21085:
Fix Version/s: 4.9.0
> Support providing absolute path for camel file creation using Camel JBang
> -
>
> Key: CAMEL-21085
> URL: https://issues.apache.org/jira/browse/CAMEL-21085
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
>Affects Versions: 4.7.0
>Reporter: Aurélien Pupier
>Priority: Major
> Fix For: 4.9.0
>
>
> currently it is failing with this kind of error:
> {noformat}
> (base) apupier@localhost:~/ws/record-gif-readme$ jbang
> '-Dcamel.jbang.version=4.7.0' camel@apache/camel init
> /home/apupier/ws/record-gif-readme/target-folder/anothersecondone.camel.yaml
> java.io.FileNotFoundException:
> ./home/apupier/ws/record-gif-readme/target-folder/anothersecondone.camel.yaml
> (No such file or directory)
> at java.base/java.io.FileOutputStream.open0(Native Method)
> at java.base/java.io.FileOutputStream.open(FileOutputStream.java:289)
> at
> java.base/java.io.FileOutputStream.(FileOutputStream.java:230)
> at
> org.apache.camel.dsl.jbang.core.commands.Init.execute(Init.java:174)
> at org.apache.camel.dsl.jbang.core.commands.Init.doCall(Init.java:82)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
> at picocli.CommandLine.executeUserObject(CommandLine.java:2045)
> at picocli.CommandLine.access$1500(CommandLine.java:148)
> at
> picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)
> at
> picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
> at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
> at picocli.CommandLine.execute(CommandLine.java:2174)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:168)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:61)
> at main.CamelJBang.main(CamelJBang.java:36)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21125) Fix issue related to flaky test MulticastRouteTest.testRoute
[
https://issues.apache.org/jira/browse/CAMEL-21125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-21125.
-
Fix Version/s: 4.8.1
Resolution: Fixed
> Fix issue related to flaky test MulticastRouteTest.testRoute
>
>
> Key: CAMEL-21125
> URL: https://issues.apache.org/jira/browse/CAMEL-21125
> Project: Camel
> Issue Type: Test
> Components: camel-opentelemetry, camel-opentracing
>Affects Versions: 4.8.0
>Reporter: Aurélien Pupier
>Priority: Minor
> Fix For: 4.8.1
>
>
> they are often failing, both in opentelemetry and observation (for instance
> failed in the last 3 run)
> {noformat}
> org.opentest4j.AssertionFailedError: There must be no leaking span after test
> ==> expected: <{}> but was:
> <{opentelemetry-trace-span-key=SdkSpan{traceId=d52e50419282179dcc22735ccdff7d12,
> spanId=077dbc4dd37b7f41,
> parentSpanContext=ImmutableSpanContext{traceId=d52e50419282179dcc22735ccdff7d12,
> spanId=b96763f030fc7cde, traceFlags=01,
> traceState=ArrayBasedTraceState{entries=[]}, remote=false, valid=true},
> name=a, kind=CLIENT, attributes=AttributesMap{data={url.scheme=seda,
> post=test, camel.uri=seda://a, component=camel-seda, pre=test, url.path=a},
> capacity=128, totalAddedValues=6},
> status=ImmutableStatusData{statusCode=UNSET, description=},
> totalRecordedEvents=0, totalRecordedLinks=0,
> startEpochNanos=1724766354455741077, endEpochNanos=1724766357417619086}}>
> at
> org.apache.camel.opentelemetry.CamelOpenTelemetryTestSupport.noLeakingContext(CamelOpenTelemetryTestSupport.java:76)
> at java.base/java.lang.reflect.Method.invoke(Method.java:580)
> at
> java.base/java.util.concurrent.RecursiveAction.exec(RecursiveAction.java:194)
> at
> java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:387)
> at
> java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1312)
> at
> java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1843)
> at
> java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1808)
> at
> java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:188)
> {noformat}
> {noformat}
> java.lang.AssertionError:
> [There must be no leaking span after test]
> Expecting actual:
>
> {opentelemetry-trace-span-key=SdkSpan{traceId=7f35d5210f352c8ebaae6b0487f78806,
> spanId=769ec88eaa654bea,
> parentSpanContext=ImmutableSpanContext{traceId=7f35d5210f352c8ebaae6b0487f78806,
> spanId=16510aefc2c96d35, traceFlags=01,
> traceState=ArrayBasedTraceState{entries=[]}, remote=false, valid=true},
> name=a, kind=CLIENT, attributes=AttributesMap{data={url.scheme=seda,
> component=camel-seda, pre=test, url.path=a, post=test, camel.uri=seda://a},
> capacity=128, totalAddedValues=6},
> status=ImmutableStatusData{statusCode=UNSET, description=},
> totalRecordedEvents=0, totalRecordedLinks=0,
> startEpochNanos=1724766241783741435, endEpochNanos=1724766244479434276},
> opentelemetry-baggage-key={},
> otelTraceContext=ImmutableSpanContext{traceId=7f35d5210f352c8ebaae6b0487f78806,
> spanId=769ec88eaa654bea, traceFlags=01,
> traceState=ArrayBasedTraceState{entries=[]}, remote=false, valid=true}}
> and:
> {}
> to refer to the same object
> at
> org.apache.camel.observation.CamelMicrometerObservationTestSupport.noLeakingContext(CamelMicrometerObservationTestSupport.java:92)
> at java.base/java.lang.reflect.Method.invoke(Method.java:580)
> at
> java.base/java.util.concurrent.RecursiveAction.exec(RecursiveAction.java:194)
> at
> java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:387)
> at
> java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1312)
> at
> java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1843)
> at
> java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1808)
> at
> java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:188)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21125) Fix issue related to flaky test MulticastRouteTest.testRoute
[
https://issues.apache.org/jira/browse/CAMEL-21125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21125:
Fix Version/s: 4.8.0
(was: 4.8.1)
> Fix issue related to flaky test MulticastRouteTest.testRoute
>
>
> Key: CAMEL-21125
> URL: https://issues.apache.org/jira/browse/CAMEL-21125
> Project: Camel
> Issue Type: Test
> Components: camel-opentelemetry, camel-opentracing
>Affects Versions: 4.8.0
>Reporter: Aurélien Pupier
>Priority: Minor
> Fix For: 4.8.0
>
>
> they are often failing, both in opentelemetry and observation (for instance
> failed in the last 3 run)
> {noformat}
> org.opentest4j.AssertionFailedError: There must be no leaking span after test
> ==> expected: <{}> but was:
> <{opentelemetry-trace-span-key=SdkSpan{traceId=d52e50419282179dcc22735ccdff7d12,
> spanId=077dbc4dd37b7f41,
> parentSpanContext=ImmutableSpanContext{traceId=d52e50419282179dcc22735ccdff7d12,
> spanId=b96763f030fc7cde, traceFlags=01,
> traceState=ArrayBasedTraceState{entries=[]}, remote=false, valid=true},
> name=a, kind=CLIENT, attributes=AttributesMap{data={url.scheme=seda,
> post=test, camel.uri=seda://a, component=camel-seda, pre=test, url.path=a},
> capacity=128, totalAddedValues=6},
> status=ImmutableStatusData{statusCode=UNSET, description=},
> totalRecordedEvents=0, totalRecordedLinks=0,
> startEpochNanos=1724766354455741077, endEpochNanos=1724766357417619086}}>
> at
> org.apache.camel.opentelemetry.CamelOpenTelemetryTestSupport.noLeakingContext(CamelOpenTelemetryTestSupport.java:76)
> at java.base/java.lang.reflect.Method.invoke(Method.java:580)
> at
> java.base/java.util.concurrent.RecursiveAction.exec(RecursiveAction.java:194)
> at
> java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:387)
> at
> java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1312)
> at
> java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1843)
> at
> java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1808)
> at
> java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:188)
> {noformat}
> {noformat}
> java.lang.AssertionError:
> [There must be no leaking span after test]
> Expecting actual:
>
> {opentelemetry-trace-span-key=SdkSpan{traceId=7f35d5210f352c8ebaae6b0487f78806,
> spanId=769ec88eaa654bea,
> parentSpanContext=ImmutableSpanContext{traceId=7f35d5210f352c8ebaae6b0487f78806,
> spanId=16510aefc2c96d35, traceFlags=01,
> traceState=ArrayBasedTraceState{entries=[]}, remote=false, valid=true},
> name=a, kind=CLIENT, attributes=AttributesMap{data={url.scheme=seda,
> component=camel-seda, pre=test, url.path=a, post=test, camel.uri=seda://a},
> capacity=128, totalAddedValues=6},
> status=ImmutableStatusData{statusCode=UNSET, description=},
> totalRecordedEvents=0, totalRecordedLinks=0,
> startEpochNanos=1724766241783741435, endEpochNanos=1724766244479434276},
> opentelemetry-baggage-key={},
> otelTraceContext=ImmutableSpanContext{traceId=7f35d5210f352c8ebaae6b0487f78806,
> spanId=769ec88eaa654bea, traceFlags=01,
> traceState=ArrayBasedTraceState{entries=[]}, remote=false, valid=true}}
> and:
> {}
> to refer to the same object
> at
> org.apache.camel.observation.CamelMicrometerObservationTestSupport.noLeakingContext(CamelMicrometerObservationTestSupport.java:92)
> at java.base/java.lang.reflect.Method.invoke(Method.java:580)
> at
> java.base/java.util.concurrent.RecursiveAction.exec(RecursiveAction.java:194)
> at
> java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:387)
> at
> java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1312)
> at
> java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1843)
> at
> java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1808)
> at
> java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:188)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21216) Apache Camel LRA does not work with Oracle MicroTX LRA coordinator
[
https://issues.apache.org/jira/browse/CAMEL-21216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21216:
Fix Version/s: 4.x
> Apache Camel LRA does not work with Oracle MicroTX LRA coordinator
> --
>
> Key: CAMEL-21216
> URL: https://issues.apache.org/jira/browse/CAMEL-21216
> Project: Camel
> Issue Type: Bug
> Components: camel-lra
>Affects Versions: 4.7.0
>Reporter: Dirk Fiedler
>Priority: Minor
> Fix For: 4.x
>
>
> {color:#00}Hi Team,{color}
> {color:#00}we are using the Apache Camel LRA components within Java
> Springboot projects to implement saga services.{color}
> {color:#00}Till now, we are using Narayana as an LRA-Coordinator. Now we
> want to switch to Oracl MicroTX {color}
> {color:#00}(https://docs.oracle.com/en/database/oracle/transaction-manager-for-microservices/24.2/tmmdg/lra-transaction-protocol.html).{color}
> {color:#00}After configuring Oracle MircoTX instead of Narayana, we are
> facing two problems within the {color}
> {color:#00}Apache Camel LRA component code.{color}
> {color:#0451a5}1){color}{color:#00} While joining an LRA Transaction, the
> payload sent by Apache Camel is URL encoded{color}
> {color:#0451a5}2){color}{color:#00} The Query parameter sent by Oracle
> LRA coordinator are url encoded, but will not be decoded by Apache Camal LRA
> (see also: CAMEL-21197){color}
> {color:#00}I will set up a branch with my suggested code changes and link
> this afterwards to this jira bug.{color}
> {color:#00}The code changes are completely backwards compatible with
> Narayana (already tested).{color}
> {color:#0451a5}1){color}{color:#00} Joining an LRA Transaction{color}
> {color:#00}The class 'LRAClient' is using 'LRAUrlBuilder' inside Method
> 'join'. All parts of the http put body are url encoded. {color}
> {color:#00}Within Oracle LRA Coordinator log i can see the incomming
> request from Apache Camel:{color}
>
> {code:java}
> ;
>
> rel=compensate,;
> rel=complete{code}
> {color:#00}This url encoded query param
> 'Camel-Saga-Complete=direct%3A%2F%2Fsaga1_sagaService_complete' will be
> encoded again on Oracle LRA Coordinator side.{color}
> {color:#00}This is causing the error message within Apache Camel
> LRA:{color}
>
> {code:java}
> o.a.c.RuntimeCamelException: Cannot join LRA at
> o.a.c.s.l.LRAClient.lambda$join$2(LRAClient.java:138) ... 10 common frames
> omitted Wrapped by: j.u.c.CompletionException:
> org.apache.camel.RuntimeCamelException: Cannot join LRA at
> j.u.c.CompletableFuture.encodeThrowable(Unknown Source) at
> j.u.c.CompletableFuture.completeThrowable(Unknown Source) at
> j.u.c.CompletableFuture$UniApply.tryFire(Unknown Source) at
> j.u.c.CompletableFuture.postComplete(Unknown Source) at
> j.u.c.CompletableFuture.postFire(Unknown Source) at
> j.u.c.CompletableFuture$UniWhenComplete.tryFire(Unknown Source) at
> j.u.c.CompletableFuture$Completion.exec(Unknown Source) at
> j.u.c.ForkJoinTask.doExec(Unknown Source) at
> j.u.c.ForkJoinPool$WorkQueue.topLevelExec(Unknown Source) at
> j.u.c.ForkJoinPool.scan(Unknown Source) at
> j.u.c.ForkJoinPool.runWorker(Unknown Source) at
> j.u.c.ForkJoinWorkerThread.run(Unknown Source){code}
>
> {color:#00}When logging the result http code and body{color}
>
> {code:java}
> LOG.error("error while joining LRA: {} / {}", response.statusCode(),
> response.body());{code}
> {color:#00}i am getting this:{color}
> {code:java}
> error while joining LRA: 400 / error: URL is double encoded{code}
> {color:#00}The problem can be solved by not url encoding the given urls
> within the joinLRA payload.{color}
>
> org.apache.camel.service.lra.LRAUrlBuilder -> query:
>
> This code should not be executed:
>
> {code:java}
> key = URLEncoder.encode(toNonnullString(key), StandardCharsets.UTF_8.name());
> value = URLEncoder.encode(toNonnullString(value),
> StandardCharsets.UTF_8.name());
> {code}
>
> {color:#0451a5}2){color}{color:#00} Decode given query parameter from
> Oracle LRA-Coordinator call{color}
> {color:#00}After solving 1), i am getting a new exception:{color}
> {code:java}
> j.l.IllegalArgumentException: URI direct%3A%2F%2Fsaga1_sagaService_complete
> is not allowed at
> o.a.c.s.l.LRASagaRoutes.verifyRequest(LRASagaRoutes.java:107) at
> o.a.c.s.p.DelegateSyncProcessor.process(DelegateSyncProcessor.java:65) at
> o.a.c.p.e.RedeliveryErrorHandler$SimpleTask.h
[jira] [Commented] (CAMEL-21231) camel-jq - The JQ library is not as active maintaned
[ https://issues.apache.org/jira/browse/CAMEL-21231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882711#comment-17882711 ] Claus Ibsen commented on CAMEL-21231: - The maintainer would like to release current as a 1.0 - so lets give him time to do that > camel-jq - The JQ library is not as active maintaned > > > Key: CAMEL-21231 > URL: https://issues.apache.org/jira/browse/CAMEL-21231 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jq >Reporter: Claus Ibsen >Priority: Minor > Fix For: 4.x > > > camel-jq uses this library > [https://github.com/eiiches/jackson-jq] > > And its not so active maintained. And last release is a -preview release and > it would be good to get it active and do a 1.0 ga release. > If it stays inactive we may consider deprecating this in Camel. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21238) camel-jbang - k8s run - Reloading project does not change route behaviour
[
https://issues.apache.org/jira/browse/CAMEL-21238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882686#comment-17882686
]
Claus Ibsen commented on CAMEL-21238:
-
Okay so reloading locally is to let quarkus trigger reloading in the same JVM
where source files are updated and its out of the box in quarkus.
Reloading in k8s can be
* same as local, need to sync source code from camel-jbang user to running k8s
container in the right folder.
* do a container rebuild and restart the container
And we can argue whether reload (dev mode) in k8s run should be supported or
not.
> camel-jbang - k8s run - Reloading project does not change route behaviour
> -
>
> Key: CAMEL-21238
> URL: https://issues.apache.org/jira/browse/CAMEL-21238
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 4.9.0
>
>
> When running a project with `--dev` like this ...
> {code}
> jbang camel kubernetes run timer-log-route.yaml --logs --dev \
> --gav=examples:timer-log:1.0.0 \
> --trait container.imagePullPolicy=IfNotPresent \
> --trait service.type=NodePort \
> --runtime=quarkus
> {code}
> I see ...
> {code}
> Reloading project due to file change: timer-log-route.yaml
> {code}
> without image re-build/deploy
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21218) camel-quarkus - BindToRegistry seems NOT to work outside RouteBuilder
[
https://issues.apache.org/jira/browse/CAMEL-21218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882685#comment-17882685
]
Claus Ibsen commented on CAMEL-21218:
-
Thanks James, we will track this ticket in CEQ and close this
> camel-quarkus - BindToRegistry seems NOT to work outside RouteBuilder
> -
>
> Key: CAMEL-21218
> URL: https://issues.apache.org/jira/browse/CAMEL-21218
> Project: Camel
> Issue Type: Bug
> Components: camel-quarkus
>Reporter: Bruno Meseguer
>Priority: Minor
> Fix For: 4.x
>
> Attachments: report.tar.gz
>
>
> It seems Camel Quarkus is not able to pick up beans defined with:
> {code:java}
> @BindToRegistry{code}
> When defined outside a RouteBuilder.
> However, if ported inside a RouteBuilder all seems good.
> Developers may want to define Beans outside the RouteBuilder class, it makes
> sense Camel Quarkus finds them when starting up.
>
> Find attached a reproduceable.
> If started with:
> {code:java}
> ./mvnw quarkus:dev{code}
> it will fail.
> Then try uncommenting the "myProcessor" code inside the RouteBuilder in the
> file "routes.java"/
> Camel Quarkus the starts and succeeds to execute.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21238) camel-jbang - k8s run - Reloading project does not change route behaviour
[
https://issues.apache.org/jira/browse/CAMEL-21238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21238:
Summary: camel-jbang - k8s run - Reloading project does not change route
behaviour (was: Reloading project does not change route behaviour)
> camel-jbang - k8s run - Reloading project does not change route behaviour
> -
>
> Key: CAMEL-21238
> URL: https://issues.apache.org/jira/browse/CAMEL-21238
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 4.9.0
>
>
> When running a project with `--dev` like this ...
> {code}
> jbang camel kubernetes run timer-log-route.yaml --logs --dev \
> --gav=examples:timer-log:1.0.0 \
> --trait container.imagePullPolicy=IfNotPresent \
> --trait service.type=NodePort \
> --runtime=quarkus
> {code}
> I see ...
> {code}
> Reloading project due to file change: timer-log-route.yaml
> {code}
> without image re-build/deploy
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21218) camel-quarkus - BindToRegistry seems NOT to work outside RouteBuilder
[
https://issues.apache.org/jira/browse/CAMEL-21218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-21218.
-
Resolution: Information Provided
> camel-quarkus - BindToRegistry seems NOT to work outside RouteBuilder
> -
>
> Key: CAMEL-21218
> URL: https://issues.apache.org/jira/browse/CAMEL-21218
> Project: Camel
> Issue Type: Bug
> Components: camel-quarkus
>Reporter: Bruno Meseguer
>Priority: Minor
> Fix For: 4.x
>
> Attachments: report.tar.gz
>
>
> It seems Camel Quarkus is not able to pick up beans defined with:
> {code:java}
> @BindToRegistry{code}
> When defined outside a RouteBuilder.
> However, if ported inside a RouteBuilder all seems good.
> Developers may want to define Beans outside the RouteBuilder class, it makes
> sense Camel Quarkus finds them when starting up.
>
> Find attached a reproduceable.
> If started with:
> {code:java}
> ./mvnw quarkus:dev{code}
> it will fail.
> Then try uncommenting the "myProcessor" code inside the RouteBuilder in the
> file "routes.java"/
> Camel Quarkus the starts and succeeds to execute.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21215) camel-jbang: unreliable export to Quarkus without lazy binding
[
https://issues.apache.org/jira/browse/CAMEL-21215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-21215.
-
Resolution: Fixed
CAMEL-21138 resolves this
> camel-jbang: unreliable export to Quarkus without lazy binding
> --
>
> Key: CAMEL-21215
> URL: https://issues.apache.org/jira/browse/CAMEL-21215
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.0
>Reporter: Otavio Rodolfo Piske
>Priority: Major
> Fix For: 4.9.0
>
> Attachments: model.java, model2.java, route-main.yaml
>
>
> Trying to export a java file with beans annotated with {{@BindToRegistry}} to
> a CEQ project, causes it to fail with:
> {{Caused by: org.apache.camel.NoSuchBeanException: No bean could be found in
> the registry for: createChatMessage of type: org.apache.camel.Processor}}
> This error is sporadic and doesn't happen 100% of the time (it seems to be
> more reproducible on shared cloud environments).
> To reproduce: save the model.java and the route-main.yaml files and run:
> {{camel export * --runtime=quarkus --gav=org.demo:agent:1.0.0
> --dep=io.quarkiverse.langchain4j:quarkus-langchain4j-core:0.17.2,io.quarkiverse.langchain4j:quarkus-langchain4j-openai:0.17.2
> --ignore-loading-error}}
> Adding {{@BindToRegistry(lazy=true)}} makes the export work reliably, but
> that generates a project that is non-buildable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21215) camel-jbang: unreliable export to Quarkus without lazy binding
[
https://issues.apache.org/jira/browse/CAMEL-21215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21215:
Fix Version/s: 4.9.0
(was: 4.x)
> camel-jbang: unreliable export to Quarkus without lazy binding
> --
>
> Key: CAMEL-21215
> URL: https://issues.apache.org/jira/browse/CAMEL-21215
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.0
>Reporter: Otavio Rodolfo Piske
>Priority: Major
> Fix For: 4.9.0
>
> Attachments: model.java, model2.java, route-main.yaml
>
>
> Trying to export a java file with beans annotated with {{@BindToRegistry}} to
> a CEQ project, causes it to fail with:
> {{Caused by: org.apache.camel.NoSuchBeanException: No bean could be found in
> the registry for: createChatMessage of type: org.apache.camel.Processor}}
> This error is sporadic and doesn't happen 100% of the time (it seems to be
> more reproducible on shared cloud environments).
> To reproduce: save the model.java and the route-main.yaml files and run:
> {{camel export * --runtime=quarkus --gav=org.demo:agent:1.0.0
> --dep=io.quarkiverse.langchain4j:quarkus-langchain4j-core:0.17.2,io.quarkiverse.langchain4j:quarkus-langchain4j-openai:0.17.2
> --ignore-loading-error}}
> Adding {{@BindToRegistry(lazy=true)}} makes the export work reliably, but
> that generates a project that is non-buildable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21218) camel-quarkus - BindToRegistry seems NOT to work outside RouteBuilder
[
https://issues.apache.org/jira/browse/CAMEL-21218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882667#comment-17882667
]
Claus Ibsen commented on CAMEL-21218:
-
James that would be good, as there would be users that may use these camel
annotations and then export to CEQ and then would be happy if it just keeps
working
> camel-quarkus - BindToRegistry seems NOT to work outside RouteBuilder
> -
>
> Key: CAMEL-21218
> URL: https://issues.apache.org/jira/browse/CAMEL-21218
> Project: Camel
> Issue Type: Bug
> Components: camel-quarkus
>Reporter: Bruno Meseguer
>Priority: Minor
> Fix For: 4.x
>
> Attachments: report.tar.gz
>
>
> It seems Camel Quarkus is not able to pick up beans defined with:
> {code:java}
> @BindToRegistry{code}
> When defined outside a RouteBuilder.
> However, if ported inside a RouteBuilder all seems good.
> Developers may want to define Beans outside the RouteBuilder class, it makes
> sense Camel Quarkus finds them when starting up.
>
> Find attached a reproduceable.
> If started with:
> {code:java}
> ./mvnw quarkus:dev{code}
> it will fail.
> Then try uncommenting the "myProcessor" code inside the RouteBuilder in the
> file "routes.java"/
> Camel Quarkus the starts and succeeds to execute.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21235) Cannot run k8s app in namespace other than default
[ https://issues.apache.org/jira/browse/CAMEL-21235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882666#comment-17882666 ] Claus Ibsen commented on CAMEL-21235: - Thanks for helping with the run k8s commands > Cannot run k8s app in namespace other than default > -- > > Key: CAMEL-21235 > URL: https://issues.apache.org/jira/browse/CAMEL-21235 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > Fix For: 4.8.1, 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21236) Explicitly enable/disable quarkus image push
[ https://issues.apache.org/jira/browse/CAMEL-21236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882665#comment-17882665 ] Claus Ibsen commented on CAMEL-21236: - Thanks I assume this ticket is done now > Explicitly enable/disable quarkus image push > > > Key: CAMEL-21236 > URL: https://issues.apache.org/jira/browse/CAMEL-21236 > Project: Camel > Issue Type: Task > Components: camel-jbang >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > Fix For: 4.9.0 > > > The quarkus default seems to push by default when > `-Dquarkus.container-image.push` is not set. For a local closter (e.g. > DockerDesktop K8s) this would not be necessary. > > The default setting for `camel k8s run` is not to push - this should be > passed on to quarkus properties -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21218) camel-quarkus - BindToRegistry seems NOT to work outside RouteBuilder
[
https://issues.apache.org/jira/browse/CAMEL-21218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21218:
Fix Version/s: 4.x
> camel-quarkus - BindToRegistry seems NOT to work outside RouteBuilder
> -
>
> Key: CAMEL-21218
> URL: https://issues.apache.org/jira/browse/CAMEL-21218
> Project: Camel
> Issue Type: Bug
> Components: camel-quarkus
>Reporter: Bruno Meseguer
>Priority: Minor
> Fix For: 4.x
>
> Attachments: report.tar.gz
>
>
> It seems Camel Quarkus is not able to pick up beans defined with:
> {code:java}
> @BindToRegistry{code}
> When defined outside a RouteBuilder.
> However, if ported inside a RouteBuilder all seems good.
> Developers may want to define Beans outside the RouteBuilder class, it makes
> sense Camel Quarkus finds them when starting up.
>
> Find attached a reproduceable.
> If started with:
> {code:java}
> ./mvnw quarkus:dev{code}
> it will fail.
> Then try uncommenting the "myProcessor" code inside the RouteBuilder in the
> file "routes.java"/
> Camel Quarkus the starts and succeeds to execute.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21235) Cannot run k8s app in namespace other than default
[ https://issues.apache.org/jira/browse/CAMEL-21235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21235: Fix Version/s: 4.8.1 4.9.0 > Cannot run k8s app in namespace other than default > -- > > Key: CAMEL-21235 > URL: https://issues.apache.org/jira/browse/CAMEL-21235 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > Fix For: 4.8.1, 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19767) camel-core: test should not catch AssertionError
[
https://issues.apache.org/jira/browse/CAMEL-19767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-19767:
Fix Version/s: 4.x
> camel-core: test should not catch AssertionError
>
>
> Key: CAMEL-19767
> URL: https://issues.apache.org/jira/browse/CAMEL-19767
> Project: Camel
> Issue Type: Task
> Components: camel-core
>Reporter: Nikita_Konovalov
>Assignee: Gaelle Fournier
>Priority: Major
> Labels: help-wanted
> Fix For: 4.x
>
>
> ??Regarding the first set of changes ...??
> ??I think catching an {{AssertionError}} is not an adequate test practice.
> That deviates from the actual purpose of the AssertionError which is to
> indicate that the test has failed.??
> ??For now, let's keep the original as is. Let's create a ticket on Apache
> Jira to note that this is a bad practice that must be fixed.??
>
> Quoting [~orpiske]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21237) Allow Endpoint DSL in Rest DSL 'to'
[
https://issues.apache.org/jira/browse/CAMEL-21237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-21237.
-
Resolution: Fixed
> Allow Endpoint DSL in Rest DSL 'to'
> ---
>
> Key: CAMEL-21237
> URL: https://issues.apache.org/jira/browse/CAMEL-21237
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Environment: The bug was detected running Camel Quarkus 3.8.6 (Camel
> 4.4.3) on Windows 10.
>Reporter: Calle Andersson
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.9.0
>
>
> Rest DSL should allow the usage of Endpoint DSL in 'to'. E.g:
> {code:java}
> .to(direct("myRoute"))
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21104) camel-jbang - Delete used files when creating a Camel project "in-place" with Camel JBang
[ https://issues.apache.org/jira/browse/CAMEL-21104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-21104. - Resolution: Fixed > camel-jbang - Delete used files when creating a Camel project "in-place" with > Camel JBang > -- > > Key: CAMEL-21104 > URL: https://issues.apache.org/jira/browse/CAMEL-21104 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Aurélien Pupier >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.9.0 > > > currently when creating a Camel project , the used files are copied to th > enew project; > When it is exported to another folder that sounds fine but when creating > in-place, the files sounds as duplicated. > it will facilitate this important use case: > - create standalone camel file(s) > - push them on a git repository > - evolve these routes > - migrate to a Maven project and stay in the same repository -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21236) Explicitly enable/disable quarkus image push
[ https://issues.apache.org/jira/browse/CAMEL-21236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21236: Fix Version/s: 4.9.0 > Explicitly enable/disable quarkus image push > > > Key: CAMEL-21236 > URL: https://issues.apache.org/jira/browse/CAMEL-21236 > Project: Camel > Issue Type: Task > Components: camel-jbang >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > Fix For: 4.9.0 > > > The quarkus default seems to push by default when > `-Dquarkus.container-image.push` is not set. For a local closter (e.g. > DockerDesktop K8s) this would not be necessary. > > The default setting for `camel k8s run` is not to push - this should be > passed on to quarkus properties -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21104) camel-jbang - Delete used files when creating a Camel project "in-place" with Camel JBang
[ https://issues.apache.org/jira/browse/CAMEL-21104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882659#comment-17882659 ] Claus Ibsen commented on CAMEL-21104: - Okay the flag is called --clean-dir camel export --gav=com.foo:acme:1.0 --runtime=camel-main --clean-dir > camel-jbang - Delete used files when creating a Camel project "in-place" with > Camel JBang > -- > > Key: CAMEL-21104 > URL: https://issues.apache.org/jira/browse/CAMEL-21104 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Aurélien Pupier >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.9.0 > > > currently when creating a Camel project , the used files are copied to th > enew project; > When it is exported to another folder that sounds fine but when creating > in-place, the files sounds as duplicated. > it will facilitate this important use case: > - create standalone camel file(s) > - push them on a git repository > - evolve these routes > - migrate to a Maven project and stay in the same repository -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-21104) camel-jbang - Delete used files when creating a Camel project "in-place" with Camel JBang
[ https://issues.apache.org/jira/browse/CAMEL-21104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-21104: --- Assignee: Claus Ibsen > camel-jbang - Delete used files when creating a Camel project "in-place" with > Camel JBang > -- > > Key: CAMEL-21104 > URL: https://issues.apache.org/jira/browse/CAMEL-21104 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Aurélien Pupier >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.9.0 > > > currently when creating a Camel project , the used files are copied to th > enew project; > When it is exported to another folder that sounds fine but when creating > in-place, the files sounds as duplicated. > it will facilitate this important use case: > - create standalone camel file(s) > - push them on a git repository > - evolve these routes > - migrate to a Maven project and stay in the same repository -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-21237) Allow Endpoint DSL in Rest DSL 'to'
[
https://issues.apache.org/jira/browse/CAMEL-21237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-21237:
---
Assignee: Claus Ibsen
> Allow Endpoint DSL in Rest DSL 'to'
> ---
>
> Key: CAMEL-21237
> URL: https://issues.apache.org/jira/browse/CAMEL-21237
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Environment: The bug was detected running Camel Quarkus 3.8.6 (Camel
> 4.4.3) on Windows 10.
>Reporter: Calle Andersson
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.9.0
>
>
> Rest DSL should allow the usage of Endpoint DSL in 'to'. E.g:
> {code:java}
> .to(direct("myRoute"))
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21234) camel-core - Log EIP to use exchange formatter for ${exchange}
[
https://issues.apache.org/jira/browse/CAMEL-21234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882597#comment-17882597
]
Claus Ibsen commented on CAMEL-21234:
-
I had to add ${logExchange} as the new function so it did not clash with
exchange as it would make it more complicated to let ${exchange} be Exchange vs
String log text.
> camel-core - Log EIP to use exchange formatter for ${exchange}
> --
>
> Key: CAMEL-21234
> URL: https://issues.apache.org/jira/browse/CAMEL-21234
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.9.0
>
>
> https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/Log.20messages/near/470945409
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21234) camel-core - Log EIP to use exchange formatter for ${exchange}
[
https://issues.apache.org/jira/browse/CAMEL-21234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-21234.
-
Resolution: Fixed
> camel-core - Log EIP to use exchange formatter for ${exchange}
> --
>
> Key: CAMEL-21234
> URL: https://issues.apache.org/jira/browse/CAMEL-21234
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.9.0
>
>
> https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/Log.20messages/near/470945409
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21237) Allow Endpoint DSL in Rest DSL 'to'
[
https://issues.apache.org/jira/browse/CAMEL-21237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21237:
Issue Type: Improvement (was: Bug)
> Allow Endpoint DSL in Rest DSL 'to'
> ---
>
> Key: CAMEL-21237
> URL: https://issues.apache.org/jira/browse/CAMEL-21237
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Environment: The bug was detected running Camel Quarkus 3.8.6 (Camel
> 4.4.3) on Windows 10.
>Reporter: Calle Andersson
>Priority: Major
> Fix For: 4.9.0
>
>
> Rest DSL should allow the usage of Endpoint DSL in 'to'. E.g:
> {code:java}
> .to(direct("myRoute"))
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-21234) camel-core - Log EIP to use exchange formatter for ${exchange}
[
https://issues.apache.org/jira/browse/CAMEL-21234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-21234:
---
Assignee: Claus Ibsen
> camel-core - Log EIP to use exchange formatter for ${exchange}
> --
>
> Key: CAMEL-21234
> URL: https://issues.apache.org/jira/browse/CAMEL-21234
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.9.0
>
>
> https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/Log.20messages/near/470945409
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21227) camel k8s run ignores output format
[ https://issues.apache.org/jira/browse/CAMEL-21227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-21227. - Resolution: Fixed > camel k8s run ignores output format > --- > > Key: CAMEL-21227 > URL: https://issues.apache.org/jira/browse/CAMEL-21227 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Minor > Fix For: 4.9.0 > > > `camel k8s run --output=json` ignores output format and prints yaml instead -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21234) camel-core - Log EIP to use exchange formatter for ${exchange}
Claus Ibsen created CAMEL-21234:
---
Summary: camel-core - Log EIP to use exchange formatter for
${exchange}
Key: CAMEL-21234
URL: https://issues.apache.org/jira/browse/CAMEL-21234
Project: Camel
Issue Type: Improvement
Components: camel-core
Reporter: Claus Ibsen
Fix For: 4.9.0
https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/Log.20messages/near/470945409
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20870) Include PR check for documentation related to Camel website in each repository
[ https://issues.apache.org/jira/browse/CAMEL-20870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20870: Priority: Minor (was: Major) > Include PR check for documentation related to Camel website in each repository > -- > > Key: CAMEL-20870 > URL: https://issues.apache.org/jira/browse/CAMEL-20870 > Project: Camel > Issue Type: Task > Components: website >Reporter: Aurélien Pupier >Priority: Minor > > it is often that the camel-website is broken due to changes in documentation > in other Camel repositories where the documentation is defined. > it will be convenient to have a PR check on each of these repositories to > avoid being in this state. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21079) onException().doTry() is confused by prior exceptions
[ https://issues.apache.org/jira/browse/CAMEL-21079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-21079. - Resolution: Abandoned > onException().doTry() is confused by prior exceptions > - > > Key: CAMEL-21079 > URL: https://issues.apache.org/jira/browse/CAMEL-21079 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 3.22.2 > Environment: Win 11 or RHEL 8 >Reporter: Petr Kuzel >Priority: Minor > Labels: error-handling > > I have observed following, if an exchange carries > an exception, like in the onException() block, then: > .log(...) > .doTry() > .removeProperty(...) > behaves very differently from: > // .log(...) > .doTry() > .removeProperty(...) > If the exchange carries an exception, then with log(), > the doTry() block body executes. Without log(), > the doTry() block body does not execute. > I'd expect that doTry() should not consider the prior exception > but it should rather consider only exceptions thrown > in the doTry() block itself, like the regular Java try block. > > (A check at the mailing list if it was a design intent has been inconclusive > so following common sense and classifying as a bug.) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21104) camel-jbang - Delete used files when creating a Camel project "in-place" with Camel JBang
[ https://issues.apache.org/jira/browse/CAMEL-21104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882363#comment-17882363 ] Claus Ibsen commented on CAMEL-21104: - Ah okay so you are not really intended to export to current dir. And if you do, then yeah we could have a `–clean` flag or something so when the export is finishing it can clean the target dir first > camel-jbang - Delete used files when creating a Camel project "in-place" with > Camel JBang > -- > > Key: CAMEL-21104 > URL: https://issues.apache.org/jira/browse/CAMEL-21104 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Aurélien Pupier >Priority: Minor > > currently when creating a Camel project , the used files are copied to th > enew project; > When it is exported to another folder that sounds fine but when creating > in-place, the files sounds as duplicated. > it will facilitate this important use case: > - create standalone camel file(s) > - push them on a git repository > - evolve these routes > - migrate to a Maven project and stay in the same repository -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21104) camel-jbang - Delete used files when creating a Camel project "in-place" with Camel JBang
[ https://issues.apache.org/jira/browse/CAMEL-21104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21104: Fix Version/s: 4.9.0 > camel-jbang - Delete used files when creating a Camel project "in-place" with > Camel JBang > -- > > Key: CAMEL-21104 > URL: https://issues.apache.org/jira/browse/CAMEL-21104 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Aurélien Pupier >Priority: Minor > Fix For: 4.9.0 > > > currently when creating a Camel project , the used files are copied to th > enew project; > When it is exported to another folder that sounds fine but when creating > in-place, the files sounds as duplicated. > it will facilitate this important use case: > - create standalone camel file(s) > - push them on a git repository > - evolve these routes > - migrate to a Maven project and stay in the same repository -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21133) camel-jbang: export a project using langchain4j-chat does not compile
[
https://issues.apache.org/jira/browse/CAMEL-21133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-21133.
-
Resolution: Fixed
This would works with 4.9 onwards
> camel-jbang: export a project using langchain4j-chat does not compile
> --
>
> Key: CAMEL-21133
> URL: https://issues.apache.org/jira/browse/CAMEL-21133
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang, camel-langchain4j-chat
>Affects Versions: 4.7.0
>Reporter: Otavio Rodolfo Piske
>Priority: Major
> Fix For: 4.9.0
>
> Attachments: Weather.java, build.log
>
>
> When trying to export a project using the export feature, the resulting
> project does not compile due to the following error (see build.log attachment
> for details).
> Step 1: export the project
> {{camel export --dependency=dev.langchain4j:langchain4j-core:0.33.0
> --dependency=dev.langchain4j:langchain4j-open-ai:0.33.0 --runtime=quarkus
> Weather.java}}
> Step 2: try to build the generated project
> {{mvn verify}}
> Result:
> Compilation fails with the following error:
> {{[error]: Build step
> io.quarkiverse.langchain4j.deployment.BeansProcessor#handleProviders threw an
> exception: io.quarkus.runtime.configuration.ConfigurationException: A
> ChatLanguageModel or StreamingChatLanguageModel bean was requested, but no
> langchain4j providers were configured. Consider adding an extension like
> 'quarkus-langchain4j-openai'}}
> The problem is that the generated project should be using
> {{io.quarkiverse.langchain4j:quarkus-langchain4j-core:0.16.4}} and
> {{io.quarkiverse.langchain4j:quarkus-langchain4j-openai:0.16.4}} instead.
> Adjusting the {{pom.xml}} file to manually replace the dependencies solve the
> problem.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21158) Add exception as variable to expression languages
[
https://issues.apache.org/jira/browse/CAMEL-21158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882360#comment-17882360
]
Claus Ibsen commented on CAMEL-21158:
-
Also added to various template languages *DONE*
> Add exception as variable to expression languages
> -
>
> Key: CAMEL-21158
> URL: https://issues.apache.org/jira/browse/CAMEL-21158
> Project: Camel
> Issue Type: Wish
> Components: came-core
>Affects Versions: 4.7.0
>Reporter: Raymond
>Priority: Minor
> Fix For: 4.9.0
>
>
> Currently, the simple language has ${exception} available as variable. When
> checking other expression languages like Groovy, JavaScript, Velocity etc.
> these are often not available.
> I tried to get the exception in those languages through the exchange variable
> which is mostly available, something like:
> exchange.getException()
> or
> exchange.exception
> But these returned null.
> It would be more convenient when the exception is directly available as a
> predefined variable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21133) camel-jbang: export a project using langchain4j-chat does not compile
[
https://issues.apache.org/jira/browse/CAMEL-21133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21133:
Fix Version/s: 4.9.0
(was: 4.x)
> camel-jbang: export a project using langchain4j-chat does not compile
> --
>
> Key: CAMEL-21133
> URL: https://issues.apache.org/jira/browse/CAMEL-21133
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang, camel-langchain4j-chat
>Affects Versions: 4.7.0
>Reporter: Otavio Rodolfo Piske
>Priority: Major
> Fix For: 4.9.0
>
> Attachments: Weather.java, build.log
>
>
> When trying to export a project using the export feature, the resulting
> project does not compile due to the following error (see build.log attachment
> for details).
> Step 1: export the project
> {{camel export --dependency=dev.langchain4j:langchain4j-core:0.33.0
> --dependency=dev.langchain4j:langchain4j-open-ai:0.33.0 --runtime=quarkus
> Weather.java}}
> Step 2: try to build the generated project
> {{mvn verify}}
> Result:
> Compilation fails with the following error:
> {{[error]: Build step
> io.quarkiverse.langchain4j.deployment.BeansProcessor#handleProviders threw an
> exception: io.quarkus.runtime.configuration.ConfigurationException: A
> ChatLanguageModel or StreamingChatLanguageModel bean was requested, but no
> langchain4j providers were configured. Consider adding an extension like
> 'quarkus-langchain4j-openai'}}
> The problem is that the generated project should be using
> {{io.quarkiverse.langchain4j:quarkus-langchain4j-core:0.16.4}} and
> {{io.quarkiverse.langchain4j:quarkus-langchain4j-openai:0.16.4}} instead.
> Adjusting the {{pom.xml}} file to manually replace the dependencies solve the
> problem.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21158) Add exception as variable to expression languages
[
https://issues.apache.org/jira/browse/CAMEL-21158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-21158.
-
Assignee: Claus Ibsen
Resolution: Fixed
> Add exception as variable to expression languages
> -
>
> Key: CAMEL-21158
> URL: https://issues.apache.org/jira/browse/CAMEL-21158
> Project: Camel
> Issue Type: Wish
> Components: came-core
>Affects Versions: 4.7.0
>Reporter: Raymond
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.9.0
>
>
> Currently, the simple language has ${exception} available as variable. When
> checking other expression languages like Groovy, JavaScript, Velocity etc.
> these are often not available.
> I tried to get the exception in those languages through the exchange variable
> which is mostly available, something like:
> exchange.getException()
> or
> exchange.exception
> But these returned null.
> It would be more convenient when the exception is directly available as a
> predefined variable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21158) Add exception as variable to expression languages
[
https://issues.apache.org/jira/browse/CAMEL-21158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882359#comment-17882359
]
Claus Ibsen commented on CAMEL-21158:
-
Added to groovy *DONE*
> Add exception as variable to expression languages
> -
>
> Key: CAMEL-21158
> URL: https://issues.apache.org/jira/browse/CAMEL-21158
> Project: Camel
> Issue Type: Wish
> Components: came-core
>Affects Versions: 4.7.0
>Reporter: Raymond
>Priority: Minor
>
> Currently, the simple language has ${exception} available as variable. When
> checking other expression languages like Groovy, JavaScript, Velocity etc.
> these are often not available.
> I tried to get the exception in those languages through the exchange variable
> which is mostly available, something like:
> exchange.getException()
> or
> exchange.exception
> But these returned null.
> It would be more convenient when the exception is directly available as a
> predefined variable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20950) camel-micrometer - Add remote counters to metrics
[ https://issues.apache.org/jira/browse/CAMEL-20950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20950: Priority: Minor (was: Major) > camel-micrometer - Add remote counters to metrics > - > > Key: CAMEL-20950 > URL: https://issues.apache.org/jira/browse/CAMEL-20950 > Project: Camel > Issue Type: Improvement > Components: camel-micrometer >Reporter: Claus Ibsen >Priority: Minor > Fix For: 4.9.0 > > > We have internal vs external counters. For example a timer is internal, and > kafka is external. We should have this information in micrometer metrics so > monitoring systems also would know this information. > For example suppose you have a small Camel integration with 2 routes: (timer > and kafka). > The timer is triggering every second, and kafka is _remote_ and thus will > only trigger when a message is received from Kafka. > If you use `camel-jbang` you can easily see this information as follows: > ```bash > $ camel get > PID NAMECAMEL PLATFORMPROFILE READY STATUS RELOAD AGE > ROUTE MSG/S TOTAL FAIL INFLIGHT LAST DELTA SINCE-LAST > 42240 cheese 4.7.0 JBang v0.116.0 dev 1/1 Running 0 1m8s > 2/2 1.01 1/65 0/0 0/0 0 -1 1s/1s/- > ``` > Here the _TOTAL_, _FAIL_, _INFLIGHT_ columns have been updated to show two > numbers separated by slash. > The number `1/65` means that there has been only 1 remote message, and 65 in > total, so that means the internal timer has triggered 64 times. -- This message was sent by Atlassian Jira (v8.20.10#820010)
