[jira] [Resolved] (CAMEL-20733) camel-catalog - Make log eip and component name more easier to see difference
[ https://issues.apache.org/jira/browse/CAMEL-20733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20733. - Resolution: Fixed > camel-catalog - Make log eip and component name more easier to see difference > - > > Key: CAMEL-20733 > URL: https://issues.apache.org/jira/browse/CAMEL-20733 > Project: Camel > Issue Type: Improvement > Components: camel-catalog >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.6.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20733) camel-catalog - Make log eip and component name more easier to see difference
Claus Ibsen created CAMEL-20733: --- Summary: camel-catalog - Make log eip and component name more easier to see difference Key: CAMEL-20733 URL: https://issues.apache.org/jira/browse/CAMEL-20733 Project: Camel Issue Type: Improvement Components: camel-catalog Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 4.6.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20731) Route coverage fails on routes with multiple doCatch blocks
[
https://issues.apache.org/jira/browse/CAMEL-20731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20731.
-
Fix Version/s: 4.0.6
4.4.3
4.6.0
(was: 4.x)
Assignee: Claus Ibsen
Resolution: Fixed
Thanks for the sample project
> Route coverage fails on routes with multiple doCatch blocks
> ---
>
> Key: CAMEL-20731
> URL: https://issues.apache.org/jira/browse/CAMEL-20731
> Project: Camel
> Issue Type: Bug
> Components: tooling
>Affects Versions: 4.0.3
>Reporter: Adriano Machado
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.0.6, 4.4.3, 4.6.0
>
> Attachments: multiple-catch-blocks-reproducer.patch
>
>
> Routes containing `doTry` with multiple `doCatch` blocks fails when running
> the code coverage mojo. An example:
> {code:java}
> http://camel.apache.org/schema/spring;>
>
>
>
>
>
> java.io.IOException
>
>
>
> java.lang.IllegalStateException
>
>
>
>
>
>
>
> {code}
> Applying the attached patch gives the following error message:
> {noformat}
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.619
> s -- in sample.camel.MultipleCatchBlocksTest
> [INFO] Running sample.camel.SampleCamelApplicationTest
> [WARNING] Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed:
> 0.008 s -- in sample.camel.SampleCamelApplicationTest
> [INFO]
> [INFO] Results:
> [INFO]
> [WARNING] Tests run: 2, Failures: 0, Errors: 0, Skipped: 1
> [INFO]
> [INFO]
> [INFO] --- camel-report:4.6.0-SNAPSHOT:route-coverage (default-cli) @
> camel-example-spring-boot-xml ---
> [INFO] Discovered 2 routes
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 17.235 s
> [INFO] Finished at: 2024-05-02T13:13:57-04:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.camel:camel-report-maven-plugin:4.6.0-SNAPSHOT:route-coverage
> (default-cli) on project camel-example-spring-boot-xml: Error during
> gathering route coverage data for route: multiple-catch-blocks: count is
> negative: -1 -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException{noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20731) Route coverage fails on routes with multiple doCatch blocks
[
https://issues.apache.org/jira/browse/CAMEL-20731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20731:
Fix Version/s: 4.x
> Route coverage fails on routes with multiple doCatch blocks
> ---
>
> Key: CAMEL-20731
> URL: https://issues.apache.org/jira/browse/CAMEL-20731
> Project: Camel
> Issue Type: Bug
> Components: tooling
>Affects Versions: 4.0.3
>Reporter: Adriano Machado
>Priority: Minor
> Fix For: 4.x
>
> Attachments: multiple-catch-blocks-reproducer.patch
>
>
> Routes containing `doTry` with multiple `doCatch` blocks fails when running
> the code coverage mojo. An example:
> {code:java}
> http://camel.apache.org/schema/spring;>
>
>
>
>
>
> java.io.IOException
>
>
>
> java.lang.IllegalStateException
>
>
>
>
>
>
>
> {code}
> Applying the attached patch gives the following error message:
> {noformat}
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.619
> s -- in sample.camel.MultipleCatchBlocksTest
> [INFO] Running sample.camel.SampleCamelApplicationTest
> [WARNING] Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed:
> 0.008 s -- in sample.camel.SampleCamelApplicationTest
> [INFO]
> [INFO] Results:
> [INFO]
> [WARNING] Tests run: 2, Failures: 0, Errors: 0, Skipped: 1
> [INFO]
> [INFO]
> [INFO] --- camel-report:4.6.0-SNAPSHOT:route-coverage (default-cli) @
> camel-example-spring-boot-xml ---
> [INFO] Discovered 2 routes
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 17.235 s
> [INFO] Finished at: 2024-05-02T13:13:57-04:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.camel:camel-report-maven-plugin:4.6.0-SNAPSHOT:route-coverage
> (default-cli) on project camel-example-spring-boot-xml: Error during
> gathering route coverage data for route: multiple-catch-blocks: count is
> negative: -1 -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException{noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20585) Camel-package-maven-plugin: generates test configurers in non-tests artifacts
[
https://issues.apache.org/jira/browse/CAMEL-20585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20585:
Fix Version/s: 4.x
(was: 4.6.0)
> Camel-package-maven-plugin: generates test configurers in non-tests artifacts
> -
>
> Key: CAMEL-20585
> URL: https://issues.apache.org/jira/browse/CAMEL-20585
> Project: Camel
> Issue Type: Bug
> Components: build system, camel-package-maven-plugin
>Affects Versions: 4.5.0
>Reporter: Jiri Ondrusek
>Priority: Major
> Fix For: 4.x
>
>
> Change
> [https://github.com/apache/camel/commit/0fb5aa31ae590eb042a1664ff18b6d5c44acc5c4#diff-8c376760c1f21c10dc4f6b051f972405cc04fc1ce9ca636a478cc5cfb8a1f51c]
> causes that for example _camel-main.jar_ contains test configurers like
> {code:java}
> org.apache.camel.main.MySecondBar, org.apache.camel.main.MySecondFoo| {code}
> As you can see
> herehttps://github.com/apache/camel/commit/0fb5aa31ae590eb042a1664ff18b6d5c44acc5c4
> different method is called.
>
> The original method was:
> {code:java}
> public static boolean updateResource(BuildContext buildContext, Path out,
> String data) {
> try {
> if (FileUtil.updateFile(out, data)) {
> refresh(buildContext, out);
> return true;
> }
> } catch (IOException e) {
> throw new IOError(e);
> }
> return false;
> {code}
> which can not create a test resource.
> Newly called method
> {code:java}
> protected boolean updateResource(Path dir, String fileName, String data) {
> boolean updated;
> updated = updateResource(buildContext, dir.resolve(fileName), data);
> if (!fileName.endsWith(".java")) {
> > Path outputDir =
> > Paths.get(project.getBuild().getOutputDirectory());
> > updated |= updateResource(buildContext,
> > outputDir.resolve(fileName), data);
> }
> return updated;
> {code}
> refreshes also resources in outputDiectorry. Therefore some test configurers
> are created during build of the artifact.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20585) Camel-package-maven-plugin: generates test configurers in non-tests artifacts
[
https://issues.apache.org/jira/browse/CAMEL-20585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20585:
Priority: Minor (was: Major)
> Camel-package-maven-plugin: generates test configurers in non-tests artifacts
> -
>
> Key: CAMEL-20585
> URL: https://issues.apache.org/jira/browse/CAMEL-20585
> Project: Camel
> Issue Type: Bug
> Components: build system, camel-package-maven-plugin
>Affects Versions: 4.5.0
>Reporter: Jiri Ondrusek
>Priority: Minor
> Fix For: 4.x
>
>
> Change
> [https://github.com/apache/camel/commit/0fb5aa31ae590eb042a1664ff18b6d5c44acc5c4#diff-8c376760c1f21c10dc4f6b051f972405cc04fc1ce9ca636a478cc5cfb8a1f51c]
> causes that for example _camel-main.jar_ contains test configurers like
> {code:java}
> org.apache.camel.main.MySecondBar, org.apache.camel.main.MySecondFoo| {code}
> As you can see
> herehttps://github.com/apache/camel/commit/0fb5aa31ae590eb042a1664ff18b6d5c44acc5c4
> different method is called.
>
> The original method was:
> {code:java}
> public static boolean updateResource(BuildContext buildContext, Path out,
> String data) {
> try {
> if (FileUtil.updateFile(out, data)) {
> refresh(buildContext, out);
> return true;
> }
> } catch (IOException e) {
> throw new IOError(e);
> }
> return false;
> {code}
> which can not create a test resource.
> Newly called method
> {code:java}
> protected boolean updateResource(Path dir, String fileName, String data) {
> boolean updated;
> updated = updateResource(buildContext, dir.resolve(fileName), data);
> if (!fileName.endsWith(".java")) {
> > Path outputDir =
> > Paths.get(project.getBuild().getOutputDirectory());
> > updated |= updateResource(buildContext,
> > outputDir.resolve(fileName), data);
> }
> return updated;
> {code}
> refreshes also resources in outputDiectorry. Therefore some test configurers
> are created during build of the artifact.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20634) Create a centralized variable for the header name CamelLangChain4jEmbeddingsVector
[ https://issues.apache.org/jira/browse/CAMEL-20634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20634: Fix Version/s: 4.7.0 (was: 4.6.0) > Create a centralized variable for the header name > CamelLangChain4jEmbeddingsVector > -- > > Key: CAMEL-20634 > URL: https://issues.apache.org/jira/browse/CAMEL-20634 > Project: Camel > Issue Type: New Feature > Components: camel-langchain4j >Affects Versions: 4.5.0 >Reporter: Zineb Bendhiba >Assignee: Zineb Bendhiba >Priority: Minor > Fix For: 4.7.0 > > > While renaming the component (cf. > https://issues.apache.org/jira/browse/CAMEL-20611), I had to change the > header 'CamelLangChainEmbeddingsVector' to 'CamelLangChain4jEmbeddingsVector' > three times: in 'langchain4j-embeddings', 'qdrant', and 'Milvus'. > If we don't extract this string into a common dependency and need to rename > it again, we will have to revisit multiple dependencies. > Perhaps it would be better to move it to the 'camel-api' module. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20609) camel-core - Using variableReceive should use a child exchange for processing
[ https://issues.apache.org/jira/browse/CAMEL-20609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20609: Fix Version/s: 4.7.0 (was: 4.6.0) > camel-core - Using variableReceive should use a child exchange for processing > - > > Key: CAMEL-20609 > URL: https://issues.apache.org/jira/browse/CAMEL-20609 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.7.0 > > > See CAMEL-20607 > When using variableReceive you want the processing to be more separated -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20732) RestDefinition does not properly handle array of primitives for` in/out types
[
https://issues.apache.org/jira/browse/CAMEL-20732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20732.
-
Resolution: Fixed
Thanks for reporting and the PR
> RestDefinition does not properly handle array of primitives for` in/out types
> -
>
> Key: CAMEL-20732
> URL: https://issues.apache.org/jira/browse/CAMEL-20732
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.4.2
>Reporter: Stefan Kalscheuer
>Priority: Minor
> Fix For: 4.4.3, 4.6.0
>
>
> This is likely a regression from CAMEL-15199 (since 3.5.0).
> Using primitive array types as in/out type in REST route definition results
> in invalid string representation of the actual type.
>
> *History*
> Noticed on a project with Camel 4.4 including SpringDoc and a route with
> outType "byte[]".
> OpenAPI/Swagger output is completely broken (i.e. empty), apparently because
> the type "null[]" is not resolvable.
> The issue is still present in latest 4.6.0-SNAPSHOT and most likely since
> 3.5.0
>
> *Analysis*
> The workaround code introduced in the referenced issue contains this branch:
> {code:java}
> if (!classType.isPrimitive()) {
> if (classType.isArray()) {
> type = StringHelper.between(classType.getName(), "[L", ";") + "[]";
> } else {
> /* ...*/{code}
> Because byte[].class.getName() returns "[B" there is nothing betwen "[L" and
> ";", so the output is "null[]".
>
> *Example*
> {code:java}
> package my.example;
> public class MyRoutes extends org.apache.camel.builder.RouteBuilder {
> @Override
> public void configure() throws Exception {
> rest()
> .get("/test")
> .outType(byte[].class)
> .produces("application/octet-stream")
> .route()
> .log("test me");
> }
> } {code}
>
> *Workarounds*
> Use boxed type, e.g. Byte[] (which correctly results in "java.lang.Byte[]")
> or specify the type as String "byte[]" directly.
>
> *Solution*
> The solution seems pretty straight forward here. I will submit a proposal
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20732) RestDefinition does not properly handle array of primitives for` in/out types
[
https://issues.apache.org/jira/browse/CAMEL-20732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20732:
Fix Version/s: 4.4.3
> RestDefinition does not properly handle array of primitives for` in/out types
> -
>
> Key: CAMEL-20732
> URL: https://issues.apache.org/jira/browse/CAMEL-20732
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.4.2
>Reporter: Stefan Kalscheuer
>Priority: Minor
> Fix For: 4.4.3, 4.6.0
>
>
> This is likely a regression from CAMEL-15199 (since 3.5.0).
> Using primitive array types as in/out type in REST route definition results
> in invalid string representation of the actual type.
>
> *History*
> Noticed on a project with Camel 4.4 including SpringDoc and a route with
> outType "byte[]".
> OpenAPI/Swagger output is completely broken (i.e. empty), apparently because
> the type "null[]" is not resolvable.
> The issue is still present in latest 4.6.0-SNAPSHOT and most likely since
> 3.5.0
>
> *Analysis*
> The workaround code introduced in the referenced issue contains this branch:
> {code:java}
> if (!classType.isPrimitive()) {
> if (classType.isArray()) {
> type = StringHelper.between(classType.getName(), "[L", ";") + "[]";
> } else {
> /* ...*/{code}
> Because byte[].class.getName() returns "[B" there is nothing betwen "[L" and
> ";", so the output is "null[]".
>
> *Example*
> {code:java}
> package my.example;
> public class MyRoutes extends org.apache.camel.builder.RouteBuilder {
> @Override
> public void configure() throws Exception {
> rest()
> .get("/test")
> .outType(byte[].class)
> .produces("application/octet-stream")
> .route()
> .log("test me");
> }
> } {code}
>
> *Workarounds*
> Use boxed type, e.g. Byte[] (which correctly results in "java.lang.Byte[]")
> or specify the type as String "byte[]" directly.
>
> *Solution*
> The solution seems pretty straight forward here. I will submit a proposal
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20732) RestDefinition does not properly handle array of primitives for` in/out types
[
https://issues.apache.org/jira/browse/CAMEL-20732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20732:
Fix Version/s: 4.6.0
> RestDefinition does not properly handle array of primitives for` in/out types
> -
>
> Key: CAMEL-20732
> URL: https://issues.apache.org/jira/browse/CAMEL-20732
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.4.2
>Reporter: Stefan Kalscheuer
>Priority: Minor
> Fix For: 4.6.0
>
>
> This is likely a regression from CAMEL-15199 (since 3.5.0).
> Using primitive array types as in/out type in REST route definition results
> in invalid string representation of the actual type.
>
> *History*
> Noticed on a project with Camel 4.4 including SpringDoc and a route with
> outType "byte[]".
> OpenAPI/Swagger output is completely broken (i.e. empty), apparently because
> the type "null[]" is not resolvable.
> The issue is still present in latest 4.6.0-SNAPSHOT and most likely since
> 3.5.0
>
> *Analysis*
> The workaround code introduced in the referenced issue contains this branch:
> {code:java}
> if (!classType.isPrimitive()) {
> if (classType.isArray()) {
> type = StringHelper.between(classType.getName(), "[L", ";") + "[]";
> } else {
> /* ...*/{code}
> Because byte[].class.getName() returns "[B" there is nothing betwen "[L" and
> ";", so the output is "null[]".
>
> *Example*
> {code:java}
> package my.example;
> public class MyRoutes extends org.apache.camel.builder.RouteBuilder {
> @Override
> public void configure() throws Exception {
> rest()
> .get("/test")
> .outType(byte[].class)
> .produces("application/octet-stream")
> .route()
> .log("test me");
> }
> } {code}
>
> *Workarounds*
> Use boxed type, e.g. Byte[] (which correctly results in "java.lang.Byte[]")
> or specify the type as String "byte[]" directly.
>
> *Solution*
> The solution seems pretty straight forward here. I will submit a proposal
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20514) camel-model - Add support for bean constructors for beans in route templates or kamelets
[ https://issues.apache.org/jira/browse/CAMEL-20514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20514. - Resolution: Fixed > camel-model - Add support for bean constructors for beans in route templates > or kamelets > > > Key: CAMEL-20514 > URL: https://issues.apache.org/jira/browse/CAMEL-20514 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.6.0 > > > https://github.com/apache/camel-karavan/discussions/1154 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20729) camel-http - cookieStore property not recognized
[
https://issues.apache.org/jira/browse/CAMEL-20729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20729.
-
Resolution: Not A Bug
> camel-http - cookieStore property not recognized
>
>
> Key: CAMEL-20729
> URL: https://issues.apache.org/jira/browse/CAMEL-20729
> Project: Camel
> Issue Type: Bug
> Components: camel-http
>Affects Versions: 4.5.0
>Reporter: Raymond
>Priority: Minor
>
> I am in the process of upgrading from 3.20.9 to 4.5.0. When I install a route
> that uses following http endpoint:
> {code:java}
> uri="http://www.testingmcafeesites.com/testcat_al.html?cookieStore=#flowCookieStorethrowExceptionOnFailure=truemaxTotalConnections=20connectionsPerRoute=2"/>
> {code}
> I get the following error:
> {code:java}
> Failed to create route HTTP_TEST at: >>>
> To[http://www.testingmcafeesites.com/testcat_al.html?cookieStore=#flowCookieStore=true=20=2]
> <<< in route:
> Route(ID_627a64ad38c74a00130006eb-ce173190-d08f-11ec-83f5-37... because of
> Failed to resolve endpoint:
> http://www.testingmcafeesites.com/testcat_al.html?connectionsPerRoute=2=%23flowCookieStore=20=true
> due to: Error binding property (cookieStore=#flowCookieStore) with name:
> cookieStore on bean:
> http://www.testingmcafeesites.com/testcat_al.html?maxTotalConnections=20=2=true=%23flowCookieStore
> with value: #flowCookieStore",{code}
> When I remove the cookieStore property the route installs and runs normally.
> The "#flowCookieStore" is binded to registry like it was in camel 3.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-20514) camel-model - Add support for bean constructors for beans in route templates or kamelets
[ https://issues.apache.org/jira/browse/CAMEL-20514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842947#comment-17842947 ] Claus Ibsen edited comment on CAMEL-20514 at 5/3/24 6:52 AM: - TODO: add constructors, factory bean/method, builder bean/method to kamelet beans *DONE* TODO: see if we can merge model for registry bean and kamelet bean into the same model/class instead of duplicates *DONE* TODO: rename RegistryBeanDefinition to a BeanFactoryDefinition *DONE* TODO: upgrade doc *DONE* was (Author: davsclaus): TODO: add constructors, factory bean/method, builder bean/method to kamelet beans *DONE* TODO: see if we can merge model for registry bean and kamelet bean into the same model/class instead of duplicates *DONE* TODO: rename RegistryBeanDefinition to a BeanFactoryDefinition *DONE* TODO: upgrade doc > camel-model - Add support for bean constructors for beans in route templates > or kamelets > > > Key: CAMEL-20514 > URL: https://issues.apache.org/jira/browse/CAMEL-20514 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.6.0 > > > https://github.com/apache/camel-karavan/discussions/1154 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-20514) camel-model - Add support for bean constructors for beans in route templates or kamelets
[ https://issues.apache.org/jira/browse/CAMEL-20514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842947#comment-17842947 ] Claus Ibsen edited comment on CAMEL-20514 at 5/3/24 5:48 AM: - TODO: add constructors, factory bean/method, builder bean/method to kamelet beans *DONE* TODO: see if we can merge model for registry bean and kamelet bean into the same model/class instead of duplicates *DONE* TODO: rename RegistryBeanDefinition to a BeanFactoryDefinition *DONE* TODO: upgrade doc was (Author: davsclaus): TODO: add constructors, factory bean/method, builder bean/method to kamelet beans *DONE* TODO: see if we can merge model for registry bean and kamelet bean into the same model/class instead of duplicates *DONE* TODO: rename RegistryBeanDefinition to a BeanInstanceDefinition TODO: upgrade doc > camel-model - Add support for bean constructors for beans in route templates > or kamelets > > > Key: CAMEL-20514 > URL: https://issues.apache.org/jira/browse/CAMEL-20514 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.6.0 > > > https://github.com/apache/camel-karavan/discussions/1154 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-20514) camel-model - Add support for bean constructors for beans in route templates or kamelets
[ https://issues.apache.org/jira/browse/CAMEL-20514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842947#comment-17842947 ] Claus Ibsen edited comment on CAMEL-20514 at 5/2/24 8:20 PM: - TODO: add constructors, factory bean/method, builder bean/method to kamelet beans *DONE* TODO: see if we can merge model for registry bean and kamelet bean into the same model/class instead of duplicates *DONE* TODO: rename RegistryBeanDefinition to a BeanInstanceDefinition TODO: upgrade doc was (Author: davsclaus): TODO: add constructors, factory bean/method, builder bean/method to kamelet beans *DONE* TODO: see if we can merge model for registry bean and kamelet bean into the same model/class instead of duplicates > camel-model - Add support for bean constructors for beans in route templates > or kamelets > > > Key: CAMEL-20514 > URL: https://issues.apache.org/jira/browse/CAMEL-20514 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.6.0 > > > https://github.com/apache/camel-karavan/discussions/1154 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20731) Route coverage fails on routes with multiple doCatch blocks
[ https://issues.apache.org/jira/browse/CAMEL-20731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843007#comment-17843007 ] Claus Ibsen commented on CAMEL-20731: - Can you try with latest 4.4.x and/or 4.5.0 release > Route coverage fails on routes with multiple doCatch blocks > --- > > Key: CAMEL-20731 > URL: https://issues.apache.org/jira/browse/CAMEL-20731 > Project: Camel > Issue Type: Bug > Components: tooling >Affects Versions: 4.0.3 >Reporter: Adriano Machado >Priority: Minor > > Routes containing `doTry` with multiple `doCatch` blocks fails when running > the code coverate mojo. An example: > ``` > > > > > > > java.io.IOException > > > > java.lang.IllegalStateException > > > > > > > ``` -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20731) Route coverage fails on routes with multiple doCatch blocks
[ https://issues.apache.org/jira/browse/CAMEL-20731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20731: Priority: Minor (was: Major) > Route coverage fails on routes with multiple doCatch blocks > --- > > Key: CAMEL-20731 > URL: https://issues.apache.org/jira/browse/CAMEL-20731 > Project: Camel > Issue Type: Bug > Components: tooling >Affects Versions: 4.0.3 >Reporter: Adriano Machado >Priority: Minor > > Routes containing `doTry` with multiple `doCatch` blocks fails when running > the code coverate mojo. An example: > ``` > > > > > > > java.io.IOException > > > > java.lang.IllegalStateException > > > > > > > ``` -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20729) camel-http - cookieStore property not recognized
[
https://issues.apache.org/jira/browse/CAMEL-20729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842954#comment-17842954
]
Claus Ibsen commented on CAMEL-20729:
-
Make sure your cookieStore bean is the correct class - it should be
org.apache.hc.client5.http.cookie.CookieStore.class
> camel-http - cookieStore property not recognized
>
>
> Key: CAMEL-20729
> URL: https://issues.apache.org/jira/browse/CAMEL-20729
> Project: Camel
> Issue Type: Bug
> Components: camel-http
>Affects Versions: 4.5.0
>Reporter: Raymond
>Priority: Minor
>
> I am in the process of upgrading from 3.20.9 to 4.5.0. When I install a route
> that uses following http endpoint:
> {code:java}
> uri="http://www.testingmcafeesites.com/testcat_al.html?cookieStore=#flowCookieStorethrowExceptionOnFailure=truemaxTotalConnections=20connectionsPerRoute=2"/>
> {code}
> I get the following error:
> {code:java}
> Failed to create route HTTP_TEST at: >>>
> To[http://www.testingmcafeesites.com/testcat_al.html?cookieStore=#flowCookieStore=true=20=2]
> <<< in route:
> Route(ID_627a64ad38c74a00130006eb-ce173190-d08f-11ec-83f5-37... because of
> Failed to resolve endpoint:
> http://www.testingmcafeesites.com/testcat_al.html?connectionsPerRoute=2=%23flowCookieStore=20=true
> due to: Error binding property (cookieStore=#flowCookieStore) with name:
> cookieStore on bean:
> http://www.testingmcafeesites.com/testcat_al.html?maxTotalConnections=20=2=true=%23flowCookieStore
> with value: #flowCookieStore",{code}
> When I remove the cookieStore property the route installs and runs normally.
> The "#flowCookieStore" is binded to registry like it was in camel 3.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20717) camel-mllp - Exception not thrown in TcpSocketConsumerRunnable line 192
[
https://issues.apache.org/jira/browse/CAMEL-20717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20717.
-
Resolution: Fixed
> camel-mllp - Exception not thrown in TcpSocketConsumerRunnable line 192
> ---
>
> Key: CAMEL-20717
> URL: https://issues.apache.org/jira/browse/CAMEL-20717
> Project: Camel
> Issue Type: Bug
> Components: camel-mllp
>Reporter: Dmitrii Kriukov
>Assignee: Dmitrii Kriukov
>Priority: Minor
> Fix For: 4.6.0
>
>
> {color:#172b4d}new MllpInvalidMessageException({color}
> {color:#172b4d} "Timeout receiving complete message payload",
> mllpBuffer.toByteArrayAndReset(), timeoutEx,
> logPhi);
> Possible fix is to reorder statements and throw the exception in the end of
> block else
> Please let me know what you think
> {color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20729) camel-http - cookieStore property not recognized
[
https://issues.apache.org/jira/browse/CAMEL-20729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20729:
Summary: camel-http - cookieStore property not recognized (was:
cookieStore property not recognized)
> camel-http - cookieStore property not recognized
>
>
> Key: CAMEL-20729
> URL: https://issues.apache.org/jira/browse/CAMEL-20729
> Project: Camel
> Issue Type: Bug
> Components: camel-http
>Affects Versions: 4.5.0
>Reporter: Raymond
>Priority: Minor
>
> I am in the process of upgrading from 3.20.9 to 4.5.0. When I install a route
> that uses following http endpoint:
> {code:java}
> uri="http://www.testingmcafeesites.com/testcat_al.html?cookieStore=#flowCookieStorethrowExceptionOnFailure=truemaxTotalConnections=20connectionsPerRoute=2"/>
> {code}
> I get the following error:
> {code:java}
> Failed to create route HTTP_TEST at: >>>
> To[http://www.testingmcafeesites.com/testcat_al.html?cookieStore=#flowCookieStore=true=20=2]
> <<< in route:
> Route(ID_627a64ad38c74a00130006eb-ce173190-d08f-11ec-83f5-37... because of
> Failed to resolve endpoint:
> http://www.testingmcafeesites.com/testcat_al.html?connectionsPerRoute=2=%23flowCookieStore=20=true
> due to: Error binding property (cookieStore=#flowCookieStore) with name:
> cookieStore on bean:
> http://www.testingmcafeesites.com/testcat_al.html?maxTotalConnections=20=2=true=%23flowCookieStore
> with value: #flowCookieStore",{code}
> When I remove the cookieStore property the route installs and runs normally.
> The "#flowCookieStore" is binded to registry like it was in camel 3.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20514) camel-model - Add support for bean constructors for beans in route templates or kamelets
[ https://issues.apache.org/jira/browse/CAMEL-20514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842947#comment-17842947 ] Claus Ibsen commented on CAMEL-20514: - TODO: add constructors, factory bean/method, builder bean/method to kamelet beans *DONE* TODO: see if we can merge model for registry bean and kamelet bean into the same model/class instead of duplicates > camel-model - Add support for bean constructors for beans in route templates > or kamelets > > > Key: CAMEL-20514 > URL: https://issues.apache.org/jira/browse/CAMEL-20514 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.6.0 > > > https://github.com/apache/camel-karavan/discussions/1154 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20514) camel-model - Add support for bean constructors for beans in route templates or kamelets
[ https://issues.apache.org/jira/browse/CAMEL-20514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20514: Fix Version/s: 4.6.0 (was: 4.x) > camel-model - Add support for bean constructors for beans in route templates > or kamelets > > > Key: CAMEL-20514 > URL: https://issues.apache.org/jira/browse/CAMEL-20514 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.6.0 > > > https://github.com/apache/camel-karavan/discussions/1154 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20514) camel-model - Add support for bean constructors for beans in route templates or kamelets
[ https://issues.apache.org/jira/browse/CAMEL-20514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-20514: --- Assignee: Claus Ibsen > camel-model - Add support for bean constructors for beans in route templates > or kamelets > > > Key: CAMEL-20514 > URL: https://issues.apache.org/jira/browse/CAMEL-20514 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.x > > > https://github.com/apache/camel-karavan/discussions/1154 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20730) camel-jbang - Parse OSGi blueprint attributes
[ https://issues.apache.org/jira/browse/CAMEL-20730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20730. - Resolution: Fixed > camel-jbang - Parse OSGi blueprint attributes > > > Key: CAMEL-20730 > URL: https://issues.apache.org/jira/browse/CAMEL-20730 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.6.0 > > > If migrating old karaf XML files we can parse and > its attribute based configuration and configure this on camelContext so users > can load old apps via jbang to assist during migration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20730) camel-jbang - Parse OSGi blueprint attributes
Claus Ibsen created CAMEL-20730: --- Summary: camel-jbang - Parse OSGi blueprint attributes Key: CAMEL-20730 URL: https://issues.apache.org/jira/browse/CAMEL-20730 Project: Camel Issue Type: Improvement Components: camel-jbang Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 4.6.0 If migrating old karaf XML files we can parse and its attribute based configuration and configure this on camelContext so users can load old apps via jbang to assist during migration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20652) camel-rest - Contract First - Make it possible to build response from example data
[ https://issues.apache.org/jira/browse/CAMEL-20652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20652. - Resolution: Fixed > camel-rest - Contract First - Make it possible to build response from example > data > -- > > Key: CAMEL-20652 > URL: https://issues.apache.org/jira/browse/CAMEL-20652 > Project: Camel > Issue Type: Improvement > Components: camel-core, rest >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.6.0 > > > If you have "mock" as missing operation then we attempt to load responses > from file system. But if none is found, we should build an empty response > based on the contract and verb. > In the contract we can find "example" for various fields such as for Pet > where there are examples for name, tag and whatnot. We can grab them from the > contract and automatic put on the response object. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18276) azure-service-bus component does not support session
[ https://issues.apache.org/jira/browse/CAMEL-18276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18276: Fix Version/s: 4.x (was: 4.6.0) > azure-service-bus component does not support session > > > Key: CAMEL-18276 > URL: https://issues.apache.org/jira/browse/CAMEL-18276 > Project: Camel > Issue Type: New Feature > Components: camel-azure >Affects Versions: 3.18.0 >Reporter: Jean-Benoît >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.x > > > Hello, > From what I could tell, the azure-servicebus component does not support > sessions. Any chance this can be added in an upcoming release? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20701) camel-kafka: simplify de-serialization of JMS headers
[
https://issues.apache.org/jira/browse/CAMEL-20701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842595#comment-17842595
]
Claus Ibsen commented on CAMEL-20701:
-
Otavio is this work done?
> camel-kafka: simplify de-serialization of JMS headers
> -
>
> Key: CAMEL-20701
> URL: https://issues.apache.org/jira/browse/CAMEL-20701
> Project: Camel
> Issue Type: Improvement
> Components: camel-kafka
>Affects Versions: 4.4.1, 4.5.0
>Reporter: Otavio Rodolfo Piske
>Assignee: Otavio Rodolfo Piske
>Priority: Minor
> Fix For: 4.6.0
>
>
> Sometimes JMS headers may be set in different data types that those expected
> by the type converter. For instance: endpoints and or users may set and/or
> transform them as strings, longs or integers (depending on the data type).
> This complicates reading that data.
> Kafka has the {{HeaderDeserializer}} option that can used for helping this
> deserialization process.
> Camel should provide a generic class to perform this de-serialization and
> serve as a model for users willing to implement more complex cases.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20724) camel-saxon: xquery fluent API does not work with namespaces (regression)
[
https://issues.apache.org/jira/browse/CAMEL-20724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20724.
-
Fix Version/s: 4.4.3
4.6.0
(was: 4.x)
Assignee: Denis Istomin
Resolution: Fixed
> camel-saxon: xquery fluent API does not work with namespaces (regression)
> -
>
> Key: CAMEL-20724
> URL: https://issues.apache.org/jira/browse/CAMEL-20724
> Project: Camel
> Issue Type: Bug
> Components: camel-saxon
>Affects Versions: 4.4.0, 4.4.1, 4.4.2, 4.5.0
>Reporter: Denis Istomin
>Assignee: Denis Istomin
>Priority: Minor
> Fix For: 4.4.3, 4.6.0
>
>
> This is a regression starting from 4.4.0
> Reproducer:
> [https://github.com/DenisIstomin/camel-xquery-ns-bug]
> Does not work:
> {code:java}
> Namespaces ns = new Namespaces("soap",
> "http://schemas.xmlsoap.org/soap/envelope/;);
> String strExpression = "exists(/soap:Envelope/soap:Header)";
> expression().xquery().expression(strExpression).resultType(String.class).namespaces(ns).end();
> {code}
> Throws exception:
> {code:java}
> net.sf.saxon.trans.XPathException: Namespace prefix 'soap' has not been
> declared
> {code}
> Workaround is to use XQueryBuilder:
> {code:java}
> XQueryBuilder xqueryBuilder = xquery(strExpression).resultType(String.class);
> xqueryBuilder.setNamespaces(ns.getNamespaces());
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-15279) Camel-AS2 - mdn message handling and also Receipt-Delivery-Option header
[ https://issues.apache.org/jira/browse/CAMEL-15279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-15279. - Resolution: Fixed Thanks Jono for your work on camel-as2 > Camel-AS2 - mdn message handling and also Receipt-Delivery-Option header > > > Key: CAMEL-15279 > URL: https://issues.apache.org/jira/browse/CAMEL-15279 > Project: Camel > Issue Type: Improvement > Components: camel-as2 >Affects Versions: 3.4.0 >Reporter: Benson Chan >Assignee: Jono Morris >Priority: Minor > Labels: help-wanted > Fix For: 4.6.0 > > Attachments: image-2020-07-08-12-36-50-232.png > > > # add an option to allow as2 producer to set the "Receipt-Delivery-Option" > header > ## both in routing and also when using AS2ClientManager.send methods > # when receiving a MDN message, the HttpMessageUtils.extractEdiPayload will > throw an exception saying invalid content type 'multipart/report' > !image-2020-07-08-12-37-58-469.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-15279) Camel-AS2 - mdn message handling and also Receipt-Delivery-Option header
[ https://issues.apache.org/jira/browse/CAMEL-15279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-15279: Fix Version/s: 4.6.0 > Camel-AS2 - mdn message handling and also Receipt-Delivery-Option header > > > Key: CAMEL-15279 > URL: https://issues.apache.org/jira/browse/CAMEL-15279 > Project: Camel > Issue Type: Improvement > Components: camel-as2 >Affects Versions: 3.4.0 >Reporter: Benson Chan >Assignee: Jono Morris >Priority: Minor > Labels: help-wanted > Fix For: 4.6.0 > > Attachments: image-2020-07-08-12-36-50-232.png > > > # add an option to allow as2 producer to set the "Receipt-Delivery-Option" > header > ## both in routing and also when using AS2ClientManager.send methods > # when receiving a MDN message, the HttpMessageUtils.extractEdiPayload will > throw an exception saying invalid content type 'multipart/report' > !image-2020-07-08-12-37-58-469.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20727) camel-azure - Data lake upload should not read content into memory
[ https://issues.apache.org/jira/browse/CAMEL-20727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20727: Fix Version/s: 4.4.3 > camel-azure - Data lake upload should not read content into memory > -- > > Key: CAMEL-20727 > URL: https://issues.apache.org/jira/browse/CAMEL-20727 > Project: Camel > Issue Type: Improvement > Components: camel-azure >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.4.3, 4.6.0 > > > The upload operation does not need the file length, but can use the input > stream as-is. Its only the append that needs to know the offset to append > from and therefore the length. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20652) camel-rest - Contract First - Make it possible to build response from example data
[ https://issues.apache.org/jira/browse/CAMEL-20652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-20652: --- Assignee: Claus Ibsen > camel-rest - Contract First - Make it possible to build response from example > data > -- > > Key: CAMEL-20652 > URL: https://issues.apache.org/jira/browse/CAMEL-20652 > Project: Camel > Issue Type: Improvement > Components: camel-core, rest >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.6.0 > > > If you have "mock" as missing operation then we attempt to load responses > from file system. But if none is found, we should build an empty response > based on the contract and verb. > In the contract we can find "example" for various fields such as for Pet > where there are examples for name, tag and whatnot. We can grab them from the > contract and automatic put on the response object. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (CAMEL-20184) OsgiDefaultCamelContext calls init() rather than build() in ctor, preventing adding routes
[ https://issues.apache.org/jira/browse/CAMEL-20184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reopened CAMEL-20184: - > OsgiDefaultCamelContext calls init() rather than build() in ctor, preventing > adding routes > -- > > Key: CAMEL-20184 > URL: https://issues.apache.org/jira/browse/CAMEL-20184 > Project: Camel > Issue Type: Bug > Components: camel-karaf >Affects Versions: 3.14.10 >Reporter: Paul McCulloch >Priority: Minor > > The call to init() was added in 3.1 with the comment "OsgiDefaultCamelContext > should init like camel-blueprint does" > (https://github.com/apache/camel/commit/a1c4b82a31108cd23409d0ee6ca4edc5b809b291) > At that time that was the case. However in 3.2 the Blueprint context was > changed to use build() > (https://github.com/apache/camel-karaf/commit/bb1f5042042fbb3e122cb533eddbc3207c3d8efe) > No equaivalent change was made to OsgiDefaultCamelContext. > The symptoms are that routes dont't get added to the context in some > circumstances. In my case I was trying to use a local copy of > https://github.com/apache/camel/blob/camel-2.x/components/camel-scr/src/main/java/org/apache/camel/scr/AbstractCamelRunner.java > too migrate a 2.x project to 3.x. > I can probably create a simple test case to recreate if required. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (CAMEL-20184) OsgiDefaultCamelContext calls init() rather than build() in ctor, preventing adding routes
[ https://issues.apache.org/jira/browse/CAMEL-20184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen closed CAMEL-20184. --- Resolution: Information Provided > OsgiDefaultCamelContext calls init() rather than build() in ctor, preventing > adding routes > -- > > Key: CAMEL-20184 > URL: https://issues.apache.org/jira/browse/CAMEL-20184 > Project: Camel > Issue Type: Bug > Components: camel-karaf >Affects Versions: 3.14.10 >Reporter: Paul McCulloch >Priority: Minor > > The call to init() was added in 3.1 with the comment "OsgiDefaultCamelContext > should init like camel-blueprint does" > (https://github.com/apache/camel/commit/a1c4b82a31108cd23409d0ee6ca4edc5b809b291) > At that time that was the case. However in 3.2 the Blueprint context was > changed to use build() > (https://github.com/apache/camel-karaf/commit/bb1f5042042fbb3e122cb533eddbc3207c3d8efe) > No equaivalent change was made to OsgiDefaultCamelContext. > The symptoms are that routes dont't get added to the context in some > circumstances. In my case I was trying to use a local copy of > https://github.com/apache/camel/blob/camel-2.x/components/camel-scr/src/main/java/org/apache/camel/scr/AbstractCamelRunner.java > too migrate a 2.x project to 3.x. > I can probably create a simple test case to recreate if required. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (CAMEL-19788) camel-karaf - Simplify BlueprintCamelStateService getState calls
[ https://issues.apache.org/jira/browse/CAMEL-19788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen closed CAMEL-19788. --- Resolution: Information Provided > camel-karaf - Simplify BlueprintCamelStateService getState calls > > > Key: CAMEL-19788 > URL: https://issues.apache.org/jira/browse/CAMEL-19788 > Project: Camel > Issue Type: Improvement > Components: camel-karaf >Reporter: Jan Filipski >Priority: Minor > > Current implementation of BlueprintCamelStateService iterates over map of > states to build list of CamelContext states. > Component key of map (bundleId concatenated with contextId) is not necessary, > because BlueprintCamelStateService can be only used in context of one bundle > (passed in bundleContext). So camel contextId can be used as a key. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (CAMEL-17600) Add camel-azure-servicebus feature
[ https://issues.apache.org/jira/browse/CAMEL-17600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen closed CAMEL-17600. --- Resolution: Information Provided Report on github instead https://github.com/apache/camel-karaf > Add camel-azure-servicebus feature > -- > > Key: CAMEL-17600 > URL: https://issues.apache.org/jira/browse/CAMEL-17600 > Project: Camel > Issue Type: Task > Components: camel-karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19788) camel-karaf - Simplify BlueprintCamelStateService getState calls
[ https://issues.apache.org/jira/browse/CAMEL-19788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842131#comment-17842131 ] Claus Ibsen commented on CAMEL-19788: - Report on github instead https://github.com/apache/camel-karaf > camel-karaf - Simplify BlueprintCamelStateService getState calls > > > Key: CAMEL-19788 > URL: https://issues.apache.org/jira/browse/CAMEL-19788 > Project: Camel > Issue Type: Improvement > Components: camel-karaf >Reporter: Jan Filipski >Priority: Minor > > Current implementation of BlueprintCamelStateService iterates over map of > states to build list of CamelContext states. > Component key of map (bundleId concatenated with contextId) is not necessary, > because BlueprintCamelStateService can be only used in context of one bundle > (passed in bundleContext). So camel contextId can be used as a key. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (CAMEL-20184) OsgiDefaultCamelContext calls init() rather than build() in ctor, preventing adding routes
[ https://issues.apache.org/jira/browse/CAMEL-20184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen closed CAMEL-20184. --- Resolution: Fixed Report on github instead https://github.com/apache/camel-karaf > OsgiDefaultCamelContext calls init() rather than build() in ctor, preventing > adding routes > -- > > Key: CAMEL-20184 > URL: https://issues.apache.org/jira/browse/CAMEL-20184 > Project: Camel > Issue Type: Bug > Components: camel-karaf >Affects Versions: 3.14.10 >Reporter: Paul McCulloch >Priority: Minor > > The call to init() was added in 3.1 with the comment "OsgiDefaultCamelContext > should init like camel-blueprint does" > (https://github.com/apache/camel/commit/a1c4b82a31108cd23409d0ee6ca4edc5b809b291) > At that time that was the case. However in 3.2 the Blueprint context was > changed to use build() > (https://github.com/apache/camel-karaf/commit/bb1f5042042fbb3e122cb533eddbc3207c3d8efe) > No equaivalent change was made to OsgiDefaultCamelContext. > The symptoms are that routes dont't get added to the context in some > circumstances. In my case I was trying to use a local copy of > https://github.com/apache/camel/blob/camel-2.x/components/camel-scr/src/main/java/org/apache/camel/scr/AbstractCamelRunner.java > too migrate a 2.x project to 3.x. > I can probably create a simple test case to recreate if required. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20724) camel-saxon: xquery fluent API does not work with namespaces (regression)
[
https://issues.apache.org/jira/browse/CAMEL-20724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842021#comment-17842021
]
Claus Ibsen commented on CAMEL-20724:
-
Can you maybe build an unit test in camel-saxon that reproduces this and send
as PR or attach as file to this JIRA
> camel-saxon: xquery fluent API does not work with namespaces (regression)
> -
>
> Key: CAMEL-20724
> URL: https://issues.apache.org/jira/browse/CAMEL-20724
> Project: Camel
> Issue Type: Bug
> Components: camel-saxon
>Affects Versions: 4.4.0, 4.4.1, 4.4.2, 4.5.0
>Reporter: Denis Istomin
>Priority: Minor
> Fix For: 4.x
>
>
> This is a regression starting from 4.4.0
> Reproducer:
> [https://github.com/DenisIstomin/camel-xquery-ns-bug]
> Does not work:
> {code:java}
> Namespaces ns = new Namespaces("soap",
> "http://schemas.xmlsoap.org/soap/envelope/;);
> String strExpression = "exists(/soap:Envelope/soap:Header)";
> expression().xquery().expression(strExpression).resultType(String.class).namespaces(ns).end();
> {code}
> Throws exception:
> {code:java}
> net.sf.saxon.trans.XPathException: Namespace prefix 'soap' has not been
> declared
> {code}
> Workaround is to use XQueryBuilder:
> {code:java}
> XQueryBuilder xqueryBuilder = xquery(strExpression).resultType(String.class);
> xqueryBuilder.setNamespaces(ns.getNamespaces());
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20724) camel-saxon: xquery fluent API does not work with namespaces (regression)
[
https://issues.apache.org/jira/browse/CAMEL-20724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20724:
Fix Version/s: 4.x
> camel-saxon: xquery fluent API does not work with namespaces (regression)
> -
>
> Key: CAMEL-20724
> URL: https://issues.apache.org/jira/browse/CAMEL-20724
> Project: Camel
> Issue Type: Bug
> Components: camel-saxon
>Affects Versions: 4.4.0, 4.4.1, 4.4.2, 4.5.0
>Reporter: Denis Istomin
>Priority: Minor
> Fix For: 4.x
>
>
> This is a regression starting from 4.4.0
> Reproducer:
> [https://github.com/DenisIstomin/camel-xquery-ns-bug]
> Does not work:
> {code:java}
> Namespaces ns = new Namespaces("soap",
> "http://schemas.xmlsoap.org/soap/envelope/;);
> String strExpression = "exists(/soap:Envelope/soap:Header)";
> expression().xquery().expression(strExpression).resultType(String.class).namespaces(ns).end();
> {code}
> Throws exception:
> {code:java}
> net.sf.saxon.trans.XPathException: Namespace prefix 'soap' has not been
> declared
> {code}
> Workaround is to use XQueryBuilder:
> {code:java}
> XQueryBuilder xqueryBuilder = xquery(strExpression).resultType(String.class);
> xqueryBuilder.setNamespaces(ns.getNamespaces());
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20724) camel-saxon: xquery fluent API does not work with namespaces (regression)
[
https://issues.apache.org/jira/browse/CAMEL-20724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20724:
Priority: Minor (was: Major)
> camel-saxon: xquery fluent API does not work with namespaces (regression)
> -
>
> Key: CAMEL-20724
> URL: https://issues.apache.org/jira/browse/CAMEL-20724
> Project: Camel
> Issue Type: Bug
> Components: camel-saxon
>Affects Versions: 4.4.0, 4.4.1, 4.4.2, 4.5.0
>Reporter: Denis Istomin
>Priority: Minor
>
> This is a regression starting from 4.4.0
> Reproducer:
> [https://github.com/DenisIstomin/camel-xquery-ns-bug]
> Does not work:
> {code:java}
> Namespaces ns = new Namespaces("soap",
> "http://schemas.xmlsoap.org/soap/envelope/;);
> String strExpression = "exists(/soap:Envelope/soap:Header)";
> expression().xquery().expression(strExpression).resultType(String.class).namespaces(ns).end();
> {code}
> Throws exception:
> {code:java}
> net.sf.saxon.trans.XPathException: Namespace prefix 'soap' has not been
> declared
> {code}
> Workaround is to use XQueryBuilder:
> {code:java}
> XQueryBuilder xqueryBuilder = xquery(strExpression).resultType(String.class);
> xqueryBuilder.setNamespaces(ns.getNamespaces());
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20721) camel-jbang - Make it possible to set logging-level per package individually from CLI
[ https://issues.apache.org/jira/browse/CAMEL-20721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20721. - Resolution: Fixed you can also configure application.properties > camel-jbang - Make it possible to set logging-level per package individually > from CLI > - > > Key: CAMEL-20721 > URL: https://issues.apache.org/jira/browse/CAMEL-20721 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.6.0 > > > So you can do something like > camel run * --logging-level=com.foo=WARN --logging-level=com.bar=DEBUG > Or come up with a new name of the CLI as logging-level is for global I think -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20721) camel-jbang - Make it possible to set logging-level per package individually from CLI
[ https://issues.apache.org/jira/browse/CAMEL-20721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20721: Fix Version/s: 4.6.0 (was: 4.x) > camel-jbang - Make it possible to set logging-level per package individually > from CLI > - > > Key: CAMEL-20721 > URL: https://issues.apache.org/jira/browse/CAMEL-20721 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.6.0 > > > So you can do something like > camel run * --logging-level=com.foo=WARN --logging-level=com.bar=DEBUG > Or come up with a new name of the CLI as logging-level is for global I think -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20721) camel-jbang - Make it possible to set logging-level per package individually from CLI
[ https://issues.apache.org/jira/browse/CAMEL-20721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-20721: --- Assignee: Claus Ibsen > camel-jbang - Make it possible to set logging-level per package individually > from CLI > - > > Key: CAMEL-20721 > URL: https://issues.apache.org/jira/browse/CAMEL-20721 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.x > > > So you can do something like > camel run * --logging-level=com.foo=WARN --logging-level=com.bar=DEBUG > Or come up with a new name of the CLI as logging-level is for global I think -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20651) camel-jbang - The open-api should use the new contract-first openapi
[ https://issues.apache.org/jira/browse/CAMEL-20651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20651. - Resolution: Fixed > camel-jbang - The open-api should use the new contract-first openapi > - > > Key: CAMEL-20651 > URL: https://issues.apache.org/jira/browse/CAMEL-20651 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.6.0 > > > Instead of code generating rest-dsl we can just use the new openapi > contract-first instead: CAMEL-20557 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20721) camel-jbang - Make it possible to set logging-level per package individually from CLI
[ https://issues.apache.org/jira/browse/CAMEL-20721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841848#comment-17841848 ] Claus Ibsen commented on CAMEL-20721: - And alternative is to copy log4j2.properties from camel-jbang, and tweak this file, and then use --loging-config-path option > camel-jbang - Make it possible to set logging-level per package individually > from CLI > - > > Key: CAMEL-20721 > URL: https://issues.apache.org/jira/browse/CAMEL-20721 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.x > > > So you can do something like > camel run * --logging-level=com.foo=WARN --logging-level=com.bar=DEBUG > Or come up with a new name of the CLI as logging-level is for global I think -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20721) camel-jbang - Make it possible to set logging-level per package individually from CLI
[ https://issues.apache.org/jira/browse/CAMEL-20721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841847#comment-17841847 ] Claus Ibsen commented on CAMEL-20721: - We can then set the logging levels like the camel cmd logger does it at runtume. > camel-jbang - Make it possible to set logging-level per package individually > from CLI > - > > Key: CAMEL-20721 > URL: https://issues.apache.org/jira/browse/CAMEL-20721 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.x > > > So you can do something like > camel run * --logging-level=com.foo=WARN --logging-level=com.bar=DEBUG > Or come up with a new name of the CLI as logging-level is for global I think -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20721) camel-jbang - Make it possible to set logging-level per package individually from CLI
Claus Ibsen created CAMEL-20721: --- Summary: camel-jbang - Make it possible to set logging-level per package individually from CLI Key: CAMEL-20721 URL: https://issues.apache.org/jira/browse/CAMEL-20721 Project: Camel Issue Type: Improvement Components: camel-jbang Reporter: Claus Ibsen Fix For: 4.x So you can do something like camel run * --logging-level=com.foo=WARN --logging-level=com.bar=DEBUG Or come up with a new name of the CLI as logging-level is for global I think -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20720) camel-jbang - Upgrade camel-k command to CK 2.3.0
[ https://issues.apache.org/jira/browse/CAMEL-20720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20720. - Resolution: Fixed > camel-jbang - Upgrade camel-k command to CK 2.3.0 > - > > Key: CAMEL-20720 > URL: https://issues.apache.org/jira/browse/CAMEL-20720 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Christoph Deppisch >Priority: Major > Fix For: 4.6.0 > > > Can you help upgrade to camel-k 2.3 crds, in parent/pom.xml > 2.3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20654) camel-spring-redis - Auto configuration of redis template
[ https://issues.apache.org/jira/browse/CAMEL-20654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841154#comment-17841154 ] Claus Ibsen commented on CAMEL-20654: - It seems that camel-spring-redis dont have configurations for different redis servers cluster/sentinel/standalone, and that it lacks some options to configure this. > camel-spring-redis - Auto configuration of redis template > - > > Key: CAMEL-20654 > URL: https://issues.apache.org/jira/browse/CAMEL-20654 > Project: Camel > Issue Type: Improvement > Components: camel-spring-redis >Reporter: Claus Ibsen >Priority: Minor > Fix For: 4.x > > > See https://github.com/apache/camel-quarkus/issues/5962 > We can make Camel able to auto configure a redis template via configuration > and use the new @bean generator for tooling support. Then all of Camel can > use this. > Just need to ensure we use a camel specific name, something ala > camel.component.redis-template.xxx -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20651) camel-jbang - The open-api should use the new contract-first openapi
[ https://issues.apache.org/jira/browse/CAMEL-20651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-20651: --- Assignee: Claus Ibsen > camel-jbang - The open-api should use the new contract-first openapi > - > > Key: CAMEL-20651 > URL: https://issues.apache.org/jira/browse/CAMEL-20651 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.6.0 > > > Instead of code generating rest-dsl we can just use the new openapi > contract-first instead: CAMEL-20557 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20698) YAML DSL Consistency question - RegistryBeanDefinition vs TemplatedRouteBeanDefinition
[
https://issues.apache.org/jira/browse/CAMEL-20698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20698.
-
Resolution: Fixed
> YAML DSL Consistency question - RegistryBeanDefinition vs
> TemplatedRouteBeanDefinition
> --
>
> Key: CAMEL-20698
> URL: https://issues.apache.org/jira/browse/CAMEL-20698
> Project: Camel
> Issue Type: Improvement
> Components: camel-yaml-dsl
>Affects Versions: 4.5.0
>Reporter: Marat Gubaidullin
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.6.0
>
> Attachments: Screenshot 2024-04-19 at 5.05.05 PM-1.png, Screenshot
> 2024-04-19 at 5.05.05 PM.png, Screenshot 2024-04-19 at 5.05.52 PM.png
>
>
> *beans* in xxx{*}.camel.yaml{*} is *RegistryBeanDefinition*
> *beans* in *kamelet* template (in my previous post) is
> *TemplatedRouteBeanDefinition*
> while they are both aimed to define beans they have different properties and
> even properties formats.
> !Screenshot 2024-04-19 at 5.05.52 PM.png|width=388,height=772!
> !Screenshot 2024-04-19 at 5.05.05 PM.png|width=645,height=582!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20681) camel-jbang - Add support for quarkus datasource
[ https://issues.apache.org/jira/browse/CAMEL-20681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841124#comment-17841124 ] Claus Ibsen commented on CAMEL-20681: - You can use camel run --runtime=quarkus and it runs inside quarkus in 4.6 onwards. But you need to add the dependencies for the database etc. > camel-jbang - Add support for quarkus datasource > > > Key: CAMEL-20681 > URL: https://issues.apache.org/jira/browse/CAMEL-20681 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Priority: Minor > Fix For: 4.x > > > To make it easy to use a quarkus specific datasource, so users can build a > prototype quickly and then later export to CEQ. > https://stackoverflow.com/questions/78328521/run-camel-k-jdbc-locally-with-jbang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20660) camel-azure-servicebus: Consumer fails to acknowledge messages
[
https://issues.apache.org/jira/browse/CAMEL-20660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841121#comment-17841121
]
Claus Ibsen commented on CAMEL-20660:
-
Try with 4.6.0 that has CAMEL-20266
> camel-azure-servicebus: Consumer fails to acknowledge messages
> --
>
> Key: CAMEL-20660
> URL: https://issues.apache.org/jira/browse/CAMEL-20660
> Project: Camel
> Issue Type: Bug
> Components: camel-azure
>Affects Versions: 4.4.0, 4.4.1, 4.5.0
>Reporter: Dylan Piergies
>Priority: Major
> Fix For: 4.x
>
>
> We have observed issues with the Service Bus consumer from Camel 4.4+ where
> consumed messages are not acknowledged/completed correctly and landing in the
> dead-letter queue, despite the Exchange having successfully delivered the
> message to its destination.
> Our routes all follow the general form:
> {{from(azureServicebus(...))}}
> {{ // ...}}
> {{ .to(https(...))}}
> {{ .log("Message delivered to...");}}
> In our logs, we are seeing the message from the final {{log}} EIP and we can
> confirm that the message has been delivered to the destination service, but
> this is often followed by a log message from the
> {{com.azure.messaging.servicebus.ServiceBusReceiverAsyncClient}} logger:
> {{Cannot perform operation 'completed' on a disposed receiver.}}
> We then see many of these messages arriving in the DLQ, once the retry count
> is exceeded.
> The issue is difficult to create a reproduction for: it is intermittent and
> occurs most frequently during a spike in message volumes.
> The issue disappears after downgrading Camel to 4.3.0.
> Whilst we do not know the root cause for sure, we suspect this may be a
> defect of CAMEL-19262, occurring if the client is closed and recreated while
> an Exchange is in flight.
> Related Zulip chat discussion:
> https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/Azure.20Service.20Bus.20Consumer.20failing.20to.20acknowledge.20messages
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20693) camel-azure-servicebus: Service Bus Listener Not Stopping After Stopping Route in Latest Camel Version(4.4.0)
[
https://issues.apache.org/jira/browse/CAMEL-20693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20693.
-
Fix Version/s: 4.6.0
Resolution: Fixed
Fixed by CAMEL-20266
> camel-azure-servicebus: Service Bus Listener Not Stopping After Stopping
> Route in Latest Camel Version(4.4.0)
> -
>
> Key: CAMEL-20693
> URL: https://issues.apache.org/jira/browse/CAMEL-20693
> Project: Camel
> Issue Type: Bug
> Components: camel-azure, camel-azure-eventhubs
>Affects Versions: 4.4.0, 4.4.1, 4.4.2
>Reporter: harshithareddye
>Priority: Major
> Fix For: 4.6.0
>
> Attachments: CamelAzureServiceBusBug.zip
>
>
> In version 4.4.0 or later of {{{}azure-servicebus{}}}, there seems to be an
> issue where the Service Bus listener continues running even after killing the
> route. This behavior is different from version 4.3.0, where the listener
> stops as expected after the route is killed.
> *Reproduction Steps:*
> # Open the attached intellij project
> # Set connectionString value in AzureServiceBusRoute.java
> # Run the DemoApplication.java
> # Let it run for a while to ensure connection is active after starting the
> route
> # After killing the route connection is lost and reconnecting again
> # Observe that the listener still continues to receive messages despite the
> route being stopped.
> # Compare this behavior with version
> 4.3.0(azure-messaging-servicebus:7.14.7), where the listener stops as
> expected after killing the route.
> # Uncomment respective dependencies in build.gradle file and see it is
> working in older version(azure-messaging-servicebus:7.14.7)
> *Expected Behavior:*
> After stopping the Camel route, the Service Bus listener should also stop
> receiving messages, as observed in version 4.3.0.
> *Actual Behavior:*
> Even after stopping the Camel route, the Service Bus listener continues to
> receive messages, indicating that it's still active.
> This behavior appears to be a regression of bug
> https://issues.apache.org/jira/browse/CAMEL-19262 of {{{}azure-servicebus{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20705) camel-core: ScheduledPollConsumer has non-atomic operations on volatile fields
[ https://issues.apache.org/jira/browse/CAMEL-20705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20705. - Resolution: Fixed > camel-core: ScheduledPollConsumer has non-atomic operations on volatile fields > -- > > Key: CAMEL-20705 > URL: https://issues.apache.org/jira/browse/CAMEL-20705 > Project: Camel > Issue Type: Task > Components: camel-core >Affects Versions: 4.6.0 >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Labels: help-wanted > Fix For: 4.6.0 > > > This can leads to incorrect results and/or corrupted information. Consider > migrating to LongAdder or AtomicInteger. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20717) camel-mllp - Exception not thrown in TcpSocketConsumerRunnable line 192
[
https://issues.apache.org/jira/browse/CAMEL-20717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20717:
Summary: camel-mllp - Exception not thrown in TcpSocketConsumerRunnable
line 192 (was: Exception not thrown in TcpSocketConsumerRunnable line 192)
> camel-mllp - Exception not thrown in TcpSocketConsumerRunnable line 192
> ---
>
> Key: CAMEL-20717
> URL: https://issues.apache.org/jira/browse/CAMEL-20717
> Project: Camel
> Issue Type: Bug
> Components: camel-mllp
>Reporter: Dmitrii Kriukov
>Assignee: Dmitrii Kriukov
>Priority: Minor
> Fix For: 4.6.0
>
>
> {color:#172b4d}new MllpInvalidMessageException({color}
> {color:#172b4d} "Timeout receiving complete message payload",
> mllpBuffer.toByteArrayAndReset(), timeoutEx,
> logPhi);
> Possible fix is to reorder statements and throw the exception in the end of
> block else
> Please let me know what you think
> {color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20717) Exception not thrown in TcpSocketConsumerRunnable line 192
[
https://issues.apache.org/jira/browse/CAMEL-20717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20717:
Fix Version/s: 4.6.0
> Exception not thrown in TcpSocketConsumerRunnable line 192
> --
>
> Key: CAMEL-20717
> URL: https://issues.apache.org/jira/browse/CAMEL-20717
> Project: Camel
> Issue Type: Bug
> Components: camel-mllp
>Reporter: Dmitrii Kriukov
>Assignee: Dmitrii Kriukov
>Priority: Minor
> Fix For: 4.6.0
>
>
> {color:#172b4d}new MllpInvalidMessageException({color}
> {color:#172b4d} "Timeout receiving complete message payload",
> mllpBuffer.toByteArrayAndReset(), timeoutEx,
> logPhi);
> Possible fix is to reorder statements and throw the exception in the end of
> block else
> Please let me know what you think
> {color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20705) camel-core: ScheduledPollConsumer has non-atomic operations on volatile fields
[ https://issues.apache.org/jira/browse/CAMEL-20705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20705: Fix Version/s: 4.6.0 > camel-core: ScheduledPollConsumer has non-atomic operations on volatile fields > -- > > Key: CAMEL-20705 > URL: https://issues.apache.org/jira/browse/CAMEL-20705 > Project: Camel > Issue Type: Task > Components: camel-core >Affects Versions: 4.6.0 >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Labels: help-wanted > Fix For: 4.6.0 > > > This can leads to incorrect results and/or corrupted information. Consider > migrating to LongAdder or AtomicInteger. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20719) camel-milvus: Exclude troublesome bulk writer related dependencies
[ https://issues.apache.org/jira/browse/CAMEL-20719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20719. - Resolution: Fixed > camel-milvus: Exclude troublesome bulk writer related dependencies > -- > > Key: CAMEL-20719 > URL: https://issues.apache.org/jira/browse/CAMEL-20719 > Project: Camel > Issue Type: Improvement > Components: camel-milvus >Reporter: James Netherton >Assignee: James Netherton >Priority: Minor > Fix For: 4.6.0 > > > Since the introduction of bulk writer support in the Milvus Java SDK, there > are various transitive dependencies that cause some pain. Mainly hadoop, > which depends on Jetty 9.x and other non-jakarta compliant & CVE affected > stuff. > Since the component does not have any bulk writer support. We could try to > add maven exclusions for unwanted transitives. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20720) camel-jbang - Upgrade camel-k command to CK 2.3.0
[ https://issues.apache.org/jira/browse/CAMEL-20720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841119#comment-17841119 ] Claus Ibsen commented on CAMEL-20720: - the jbang command tests fails when upgrading > camel-jbang - Upgrade camel-k command to CK 2.3.0 > - > > Key: CAMEL-20720 > URL: https://issues.apache.org/jira/browse/CAMEL-20720 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Christoph Deppisch >Priority: Major > Fix For: 4.6.0 > > > Can you help upgrade to camel-k 2.3 crds, in parent/pom.xml > 2.3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20720) camel-jbang - Upgrade camel-k command to CK 2.3.0
Claus Ibsen created CAMEL-20720: --- Summary: camel-jbang - Upgrade camel-k command to CK 2.3.0 Key: CAMEL-20720 URL: https://issues.apache.org/jira/browse/CAMEL-20720 Project: Camel Issue Type: Dependency upgrade Components: camel-jbang Reporter: Claus Ibsen Assignee: Christoph Deppisch Fix For: 4.6.0 Can you help upgrade to camel-k 2.3 crds, in parent/pom.xml 2.3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20698) YAML DSL Consistency question - RegistryBeanDefinition vs TemplatedRouteBeanDefinition
[
https://issues.apache.org/jira/browse/CAMEL-20698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20698:
Fix Version/s: 4.6.0
> YAML DSL Consistency question - RegistryBeanDefinition vs
> TemplatedRouteBeanDefinition
> --
>
> Key: CAMEL-20698
> URL: https://issues.apache.org/jira/browse/CAMEL-20698
> Project: Camel
> Issue Type: Improvement
> Components: camel-yaml-dsl
>Affects Versions: 4.5.0
>Reporter: Marat Gubaidullin
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.6.0
>
> Attachments: Screenshot 2024-04-19 at 5.05.05 PM-1.png, Screenshot
> 2024-04-19 at 5.05.05 PM.png, Screenshot 2024-04-19 at 5.05.52 PM.png
>
>
> *beans* in xxx{*}.camel.yaml{*} is *RegistryBeanDefinition*
> *beans* in *kamelet* template (in my previous post) is
> *TemplatedRouteBeanDefinition*
> while they are both aimed to define beans they have different properties and
> even properties formats.
> !Screenshot 2024-04-19 at 5.05.52 PM.png|width=388,height=772!
> !Screenshot 2024-04-19 at 5.05.05 PM.png|width=645,height=582!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-20698) YAML DSL Consistency question - RegistryBeanDefinition vs TemplatedRouteBeanDefinition
[
https://issues.apache.org/jira/browse/CAMEL-20698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-20698:
---
Assignee: Claus Ibsen
> YAML DSL Consistency question - RegistryBeanDefinition vs
> TemplatedRouteBeanDefinition
> --
>
> Key: CAMEL-20698
> URL: https://issues.apache.org/jira/browse/CAMEL-20698
> Project: Camel
> Issue Type: Improvement
> Components: camel-yaml-dsl
>Affects Versions: 4.5.0
>Reporter: Marat Gubaidullin
>Assignee: Claus Ibsen
>Priority: Minor
> Attachments: Screenshot 2024-04-19 at 5.05.05 PM-1.png, Screenshot
> 2024-04-19 at 5.05.05 PM.png, Screenshot 2024-04-19 at 5.05.52 PM.png
>
>
> *beans* in xxx{*}.camel.yaml{*} is *RegistryBeanDefinition*
> *beans* in *kamelet* template (in my previous post) is
> *TemplatedRouteBeanDefinition*
> while they are both aimed to define beans they have different properties and
> even properties formats.
> !Screenshot 2024-04-19 at 5.05.52 PM.png|width=388,height=772!
> !Screenshot 2024-04-19 at 5.05.05 PM.png|width=645,height=582!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20698) YAML DSL Consistency question - RegistryBeanDefinition vs TemplatedRouteBeanDefinition
[
https://issues.apache.org/jira/browse/CAMEL-20698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841094#comment-17841094
]
Claus Ibsen commented on CAMEL-20698:
-
And the "property" array could very well be removed in yaml-dsl and maybe as
well in the xml-dsl
> YAML DSL Consistency question - RegistryBeanDefinition vs
> TemplatedRouteBeanDefinition
> --
>
> Key: CAMEL-20698
> URL: https://issues.apache.org/jira/browse/CAMEL-20698
> Project: Camel
> Issue Type: Improvement
> Components: camel-yaml-dsl
>Affects Versions: 4.5.0
>Reporter: Marat Gubaidullin
>Priority: Minor
> Attachments: Screenshot 2024-04-19 at 5.05.05 PM-1.png, Screenshot
> 2024-04-19 at 5.05.05 PM.png, Screenshot 2024-04-19 at 5.05.52 PM.png
>
>
> *beans* in xxx{*}.camel.yaml{*} is *RegistryBeanDefinition*
> *beans* in *kamelet* template (in my previous post) is
> *TemplatedRouteBeanDefinition*
> while they are both aimed to define beans they have different properties and
> even properties formats.
> !Screenshot 2024-04-19 at 5.05.52 PM.png|width=388,height=772!
> !Screenshot 2024-04-19 at 5.05.05 PM.png|width=645,height=582!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20698) YAML DSL Consistency question - RegistryBeanDefinition vs TemplatedRouteBeanDefinition
[
https://issues.apache.org/jira/browse/CAMEL-20698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841092#comment-17841092
]
Claus Ibsen commented on CAMEL-20698:
-
The "property" is there because of XML DSL, where you need to define them as
And in yaml you can use key: value style:
properties:
aaa: blah
bbb: 123
https://camel.apache.org/components/4.4.x/others/java-xml-io-dsl.html
> YAML DSL Consistency question - RegistryBeanDefinition vs
> TemplatedRouteBeanDefinition
> --
>
> Key: CAMEL-20698
> URL: https://issues.apache.org/jira/browse/CAMEL-20698
> Project: Camel
> Issue Type: Improvement
> Components: camel-yaml-dsl
>Affects Versions: 4.5.0
>Reporter: Marat Gubaidullin
>Priority: Minor
> Attachments: Screenshot 2024-04-19 at 5.05.05 PM-1.png, Screenshot
> 2024-04-19 at 5.05.05 PM.png, Screenshot 2024-04-19 at 5.05.52 PM.png
>
>
> *beans* in xxx{*}.camel.yaml{*} is *RegistryBeanDefinition*
> *beans* in *kamelet* template (in my previous post) is
> *TemplatedRouteBeanDefinition*
> while they are both aimed to define beans they have different properties and
> even properties formats.
> !Screenshot 2024-04-19 at 5.05.52 PM.png|width=388,height=772!
> !Screenshot 2024-04-19 at 5.05.05 PM.png|width=645,height=582!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20712) camel-quickfix - Exception not thrown in MessagePredicate line 62
[
https://issues.apache.org/jira/browse/CAMEL-20712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20712.
-
Resolution: Duplicate
> camel-quickfix - Exception not thrown in MessagePredicate line 62
> -
>
> Key: CAMEL-20712
> URL: https://issues.apache.org/jira/browse/CAMEL-20712
> Project: Camel
> Issue Type: Bug
> Components: camel-quickfix
>Reporter: Dmitrii Kriukov
>Assignee: Dmitrii Kriukov
>Priority: Minor
>
> RuntimeCamelException.wrapRuntimeCamelException(e){color:#cc7832};{color}
> If it's expected to throw it, please let me know - I will create a PR
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20708) 'client' var in JiraEndpoint is used dore double lock and misses volatile keyword
[ https://issues.apache.org/jira/browse/CAMEL-20708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20708. - Resolution: Not A Bug > 'client' var in JiraEndpoint is used dore double lock and misses volatile > keyword > - > > Key: CAMEL-20708 > URL: https://issues.apache.org/jira/browse/CAMEL-20708 > Project: Camel > Issue Type: Bug > Components: camel-jira >Reporter: Dmitrii Kriukov >Assignee: Dmitrii Kriukov >Priority: Major > > Line 122 in JiraEndpoint -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20717) Exception not thrown in TcpSocketConsumerRunnable line 192
[
https://issues.apache.org/jira/browse/CAMEL-20717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20717:
Priority: Minor (was: Major)
> Exception not thrown in TcpSocketConsumerRunnable line 192
> --
>
> Key: CAMEL-20717
> URL: https://issues.apache.org/jira/browse/CAMEL-20717
> Project: Camel
> Issue Type: Bug
> Components: camel-mllp
>Reporter: Dmitrii Kriukov
>Assignee: Dmitrii Kriukov
>Priority: Minor
>
> {color:#172b4d}new MllpInvalidMessageException({color}
> {color:#172b4d} "Timeout receiving complete message payload",
> mllpBuffer.toByteArrayAndReset(), timeoutEx,
> logPhi);
> Possible fix is to reorder statements and throw the exception in the end of
> block else
> Please let me know what you think
> {color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20699) camel-azure-servicebus: Broker properties not propagated to Camel Exchange
[ https://issues.apache.org/jira/browse/CAMEL-20699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20699. - Resolution: Fixed > camel-azure-servicebus: Broker properties not propagated to Camel Exchange > -- > > Key: CAMEL-20699 > URL: https://issues.apache.org/jira/browse/CAMEL-20699 > Project: Camel > Issue Type: Bug > Components: camel-azure >Affects Versions: 4.4.2, 4.5.0 >Reporter: Dylan Piergies >Priority: Major > Fix For: 4.4.3, 4.6.0 > > > Broker properties are not propagated to the Camel Exchange, because they are > overwritten by the application properties within the consumer code. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20691) camel-azure-servicebus: Broker properties should not be propagated into application properties
[ https://issues.apache.org/jira/browse/CAMEL-20691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20691. - Resolution: Fixed > camel-azure-servicebus: Broker properties should not be propagated into > application properties > -- > > Key: CAMEL-20691 > URL: https://issues.apache.org/jira/browse/CAMEL-20691 > Project: Camel > Issue Type: Bug > Components: camel-azure >Affects Versions: 4.4.2, 4.5.0 >Reporter: Dylan Piergies >Priority: Major > Fix For: 4.4.3, 4.6.0 > > > The change to propagate Camel Exchange headers into Service Bus message > application properties did not take into account that the broker properties > (and the application properties map itself) should not be added to the > application properties map. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20717) Exception not thrown in TcpSocketConsumerRunnable line 192
[
https://issues.apache.org/jira/browse/CAMEL-20717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841086#comment-17841086
]
Claus Ibsen commented on CAMEL-20717:
-
You dont need to create a new JIRA for every small things. Maybe create 1 jira
and just add comments for what you find.
The JIRA are for what matters for end users mostly so they can see what they
may be aware of when upgrading.
> Exception not thrown in TcpSocketConsumerRunnable line 192
> --
>
> Key: CAMEL-20717
> URL: https://issues.apache.org/jira/browse/CAMEL-20717
> Project: Camel
> Issue Type: Bug
> Components: camel-mllp
>Reporter: Dmitrii Kriukov
>Assignee: Dmitrii Kriukov
>Priority: Major
>
> {color:#172b4d}new MllpInvalidMessageException({color}
> {color:#172b4d} "Timeout receiving complete message payload",
> mllpBuffer.toByteArrayAndReset(), timeoutEx,
> logPhi);
> Possible fix is to reorder statements and throw the exception in the end of
> block else
> Please let me know what you think
> {color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20718) [camel-kafka] Fix JMSRedelivered in JMSDeserializer
[ https://issues.apache.org/jira/browse/CAMEL-20718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20718. - Resolution: Fixed > [camel-kafka] Fix JMSRedelivered in JMSDeserializer > --- > > Key: CAMEL-20718 > URL: https://issues.apache.org/jira/browse/CAMEL-20718 > Project: Camel > Issue Type: Bug > Components: camel-kafka >Affects Versions: 4.6.0 >Reporter: Marco Carletti >Assignee: Marco Carletti >Priority: Minor > Fix For: 4.6.0 > > > Since > [JMSRedelivered|https://camel.apache.org/components/4.4.x/jms-component.html#_endpoint_header_JMSRedelivered] > is boolean, need to convert bytes to boolean instead of int -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20718) [camel-kafka] Fix JMSRedelivered in JMSDeserializer
[ https://issues.apache.org/jira/browse/CAMEL-20718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841070#comment-17841070 ] Claus Ibsen commented on CAMEL-20718: - this is only on main branch so no backport needed > [camel-kafka] Fix JMSRedelivered in JMSDeserializer > --- > > Key: CAMEL-20718 > URL: https://issues.apache.org/jira/browse/CAMEL-20718 > Project: Camel > Issue Type: Bug > Components: camel-kafka >Affects Versions: 4.6.0 >Reporter: Marco Carletti >Assignee: Marco Carletti >Priority: Minor > Fix For: 4.6.0 > > > Since > [JMSRedelivered|https://camel.apache.org/components/4.4.x/jms-component.html#_endpoint_header_JMSRedelivered] > is boolean, need to convert bytes to boolean instead of int -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20718) [camel-kafka] Fix JMSRedelivered in JMSDeserializer
[ https://issues.apache.org/jira/browse/CAMEL-20718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841069#comment-17841069 ] Claus Ibsen commented on CAMEL-20718: - Also add JMSCorrelationIDAsBytes and change JMSCorrelationID to be string > [camel-kafka] Fix JMSRedelivered in JMSDeserializer > --- > > Key: CAMEL-20718 > URL: https://issues.apache.org/jira/browse/CAMEL-20718 > Project: Camel > Issue Type: Bug > Components: camel-kafka >Affects Versions: 4.6.0 >Reporter: Marco Carletti >Assignee: Marco Carletti >Priority: Minor > Fix For: 4.6.0 > > > Since > [JMSRedelivered|https://camel.apache.org/components/4.4.x/jms-component.html#_endpoint_header_JMSRedelivered] > is boolean, need to convert bytes to boolean instead of int -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20718) [camel-kafka] Fix JMSRedelivered in JMSDeserializer
[ https://issues.apache.org/jira/browse/CAMEL-20718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20718: Priority: Minor (was: Major) > [camel-kafka] Fix JMSRedelivered in JMSDeserializer > --- > > Key: CAMEL-20718 > URL: https://issues.apache.org/jira/browse/CAMEL-20718 > Project: Camel > Issue Type: Bug > Components: camel-kafka >Affects Versions: 4.6.0 >Reporter: Marco Carletti >Assignee: Marco Carletti >Priority: Minor > Fix For: 4.6.0 > > > Since > [JMSRedelivered|https://camel.apache.org/components/4.4.x/jms-component.html#_endpoint_header_JMSRedelivered] > is boolean, need to convert bytes to boolean instead of int -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20718) [camel-kafka] Fix JMSRedelivered in JMSDeserializer
[ https://issues.apache.org/jira/browse/CAMEL-20718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20718: Affects Version/s: 4.6.0 (was: 4.0.5) (was: 4.4.2) > [camel-kafka] Fix JMSRedelivered in JMSDeserializer > --- > > Key: CAMEL-20718 > URL: https://issues.apache.org/jira/browse/CAMEL-20718 > Project: Camel > Issue Type: Bug > Components: camel-kafka >Affects Versions: 4.6.0 >Reporter: Marco Carletti >Assignee: Marco Carletti >Priority: Major > Fix For: 4.6.0 > > > Since > [JMSRedelivered|https://camel.apache.org/components/4.4.x/jms-component.html#_endpoint_header_JMSRedelivered] > is boolean, need to convert bytes to boolean instead of int -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20718) [camel-kafka] Fix JMSRedelivered in JMSDeserializer
[ https://issues.apache.org/jira/browse/CAMEL-20718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20718: Fix Version/s: (was: 4.4.3) (was: 4.0.6) > [camel-kafka] Fix JMSRedelivered in JMSDeserializer > --- > > Key: CAMEL-20718 > URL: https://issues.apache.org/jira/browse/CAMEL-20718 > Project: Camel > Issue Type: Bug > Components: camel-kafka >Affects Versions: 4.0.5, 4.4.2 >Reporter: Marco Carletti >Assignee: Marco Carletti >Priority: Major > Fix For: 4.6.0 > > > Since > [JMSRedelivered|https://camel.apache.org/components/4.4.x/jms-component.html#_endpoint_header_JMSRedelivered] > is boolean, need to convert bytes to boolean instead of int -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20718) [camel-kafka] Fix JMSRedelivered in JMSDeserializer
[ https://issues.apache.org/jira/browse/CAMEL-20718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20718: Affects Version/s: (was: 4.5.0) > [camel-kafka] Fix JMSRedelivered in JMSDeserializer > --- > > Key: CAMEL-20718 > URL: https://issues.apache.org/jira/browse/CAMEL-20718 > Project: Camel > Issue Type: Bug > Components: camel-kafka >Affects Versions: 4.0.5, 4.4.2 >Reporter: Marco Carletti >Assignee: Marco Carletti >Priority: Major > > Since > [JMSRedelivered|https://camel.apache.org/components/4.4.x/jms-component.html#_endpoint_header_JMSRedelivered] > is boolean, need to convert bytes to boolean instead of int -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20718) [camel-kafka] Fix JMSRedelivered in JMSDeserializer
[ https://issues.apache.org/jira/browse/CAMEL-20718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20718: Fix Version/s: 4.0.6 4.4.3 4.6.0 > [camel-kafka] Fix JMSRedelivered in JMSDeserializer > --- > > Key: CAMEL-20718 > URL: https://issues.apache.org/jira/browse/CAMEL-20718 > Project: Camel > Issue Type: Bug > Components: camel-kafka >Affects Versions: 4.0.5, 4.4.2 >Reporter: Marco Carletti >Assignee: Marco Carletti >Priority: Major > Fix For: 4.0.6, 4.4.3, 4.6.0 > > > Since > [JMSRedelivered|https://camel.apache.org/components/4.4.x/jms-component.html#_endpoint_header_JMSRedelivered] > is boolean, need to convert bytes to boolean instead of int -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20716) camel-quickfix - Exception not thrown in FixMessageRouter line 102
[
https://issues.apache.org/jira/browse/CAMEL-20716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20716.
-
Resolution: Fixed
> camel-quickfix - Exception not thrown in FixMessageRouter line 102
> --
>
> Key: CAMEL-20716
> URL: https://issues.apache.org/jira/browse/CAMEL-20716
> Project: Camel
> Issue Type: Bug
> Components: camel-quickfix
>Reporter: Dmitrii Kriukov
>Assignee: Dmitrii Kriukov
>Priority: Minor
> Fix For: 4.6.0
>
>
> RuntimeCamelException.wrapRuntimeCamelException(e){color:#cc7832};
> {color:#172b4d}I will create a PR{color}
> {color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20716) camel-quickfix - Exception not thrown in FixMessageRouter line 102
[
https://issues.apache.org/jira/browse/CAMEL-20716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20716:
Priority: Minor (was: Major)
> camel-quickfix - Exception not thrown in FixMessageRouter line 102
> --
>
> Key: CAMEL-20716
> URL: https://issues.apache.org/jira/browse/CAMEL-20716
> Project: Camel
> Issue Type: Bug
> Components: camel-quickfix
>Reporter: Dmitrii Kriukov
>Assignee: Dmitrii Kriukov
>Priority: Minor
>
> RuntimeCamelException.wrapRuntimeCamelException(e){color:#cc7832};
> {color:#172b4d}I will create a PR{color}
> {color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20716) camel-quickfix - Exception not thrown in FixMessageRouter line 102
[
https://issues.apache.org/jira/browse/CAMEL-20716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20716:
Fix Version/s: 4.6.0
> camel-quickfix - Exception not thrown in FixMessageRouter line 102
> --
>
> Key: CAMEL-20716
> URL: https://issues.apache.org/jira/browse/CAMEL-20716
> Project: Camel
> Issue Type: Bug
> Components: camel-quickfix
>Reporter: Dmitrii Kriukov
>Assignee: Dmitrii Kriukov
>Priority: Minor
> Fix For: 4.6.0
>
>
> RuntimeCamelException.wrapRuntimeCamelException(e){color:#cc7832};
> {color:#172b4d}I will create a PR{color}
> {color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-20266) camel-azure-eventbus - Use high-level client (ServiceBusProcessorClient)
[ https://issues.apache.org/jira/browse/CAMEL-20266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-20266: --- Assignee: Dylan Piergies > camel-azure-eventbus - Use high-level client (ServiceBusProcessorClient) > > > Key: CAMEL-20266 > URL: https://issues.apache.org/jira/browse/CAMEL-20266 > Project: Camel > Issue Type: Improvement > Components: camel-azure >Reporter: Claus Ibsen >Assignee: Dylan Piergies >Priority: Major > Fix For: 4.6.0 > > > Instead of low-level client that is reactor flux based :( then use the high > level that has HA built-in and take care of reconnecting on error and much > more. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20266) camel-azure-eventbus - Use high-level client (ServiceBusProcessorClient)
[ https://issues.apache.org/jira/browse/CAMEL-20266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20266. - Resolution: Fixed Thanks Dylan. More help with azure is surely welcome > camel-azure-eventbus - Use high-level client (ServiceBusProcessorClient) > > > Key: CAMEL-20266 > URL: https://issues.apache.org/jira/browse/CAMEL-20266 > Project: Camel > Issue Type: Improvement > Components: camel-azure >Reporter: Claus Ibsen >Assignee: Dylan Piergies >Priority: Major > Fix For: 4.6.0 > > > Instead of low-level client that is reactor flux based :( then use the high > level that has HA built-in and take care of reconnecting on error and much > more. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20700) camel-core: ReflectionHelper.setField may fail for numeric type fields
[
https://issues.apache.org/jira/browse/CAMEL-20700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20700.
-
Resolution: Fixed
> camel-core: ReflectionHelper.setField may fail for numeric type fields
> --
>
> Key: CAMEL-20700
> URL: https://issues.apache.org/jira/browse/CAMEL-20700
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.3.0, 4.4.0, 4.5.0
>Reporter: James Netherton
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.4.3, 4.6.0
>
>
> Originally reported here:
> [https://camel.zulipchat.com/#narrow/stream/257302-camel-quarkus/topic/PropertyInject.20failure.20in.20CxfConfigurer]
> If you use @PropertyInject like:
> {code:java}
> public class Foo {
> @PropertyInject(value = "1")
> private Integer bar;
> }
> {code}
> Then you get an exception like:
> {code:java}
> java.lang.UnsupportedOperationException: Cannot inject value of class: class
> java.lang.Integer into: private java.lang.Integer
> {code}
> The original exception is swallowed, but it's something like:
> {code:java}
> IllegalArgumentException: Can not set java.lang.Integer field to int(1)
> {code}
> You can't use Field.setInt etc where the field type is not a primitive. You
> have to use Field.set in that case.
> [https://docs.oracle.com/javase/tutorial/reflect/member/fieldTrouble.html]
> Maybe it's related to this change:
> [https://github.com/apache/camel/commit/df19aec009164ba821c60518651dfc5eda3aee7d]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20700) camel-core: ReflectionHelper.setField may fail for numeric type fields
[
https://issues.apache.org/jira/browse/CAMEL-20700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20700:
Fix Version/s: 4.4.3
> camel-core: ReflectionHelper.setField may fail for numeric type fields
> --
>
> Key: CAMEL-20700
> URL: https://issues.apache.org/jira/browse/CAMEL-20700
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.3.0, 4.4.0, 4.5.0
>Reporter: James Netherton
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.4.3, 4.6.0
>
>
> Originally reported here:
> [https://camel.zulipchat.com/#narrow/stream/257302-camel-quarkus/topic/PropertyInject.20failure.20in.20CxfConfigurer]
> If you use @PropertyInject like:
> {code:java}
> public class Foo {
> @PropertyInject(value = "1")
> private Integer bar;
> }
> {code}
> Then you get an exception like:
> {code:java}
> java.lang.UnsupportedOperationException: Cannot inject value of class: class
> java.lang.Integer into: private java.lang.Integer
> {code}
> The original exception is swallowed, but it's something like:
> {code:java}
> IllegalArgumentException: Can not set java.lang.Integer field to int(1)
> {code}
> You can't use Field.setInt etc where the field type is not a primitive. You
> have to use Field.set in that case.
> [https://docs.oracle.com/javase/tutorial/reflect/member/fieldTrouble.html]
> Maybe it's related to this change:
> [https://github.com/apache/camel/commit/df19aec009164ba821c60518651dfc5eda3aee7d]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-20700) camel-core: ReflectionHelper.setField may fail for numeric type fields
[
https://issues.apache.org/jira/browse/CAMEL-20700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-20700:
---
Assignee: Claus Ibsen
> camel-core: ReflectionHelper.setField may fail for numeric type fields
> --
>
> Key: CAMEL-20700
> URL: https://issues.apache.org/jira/browse/CAMEL-20700
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.3.0, 4.4.0, 4.5.0
>Reporter: James Netherton
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.6.0
>
>
> Originally reported here:
> [https://camel.zulipchat.com/#narrow/stream/257302-camel-quarkus/topic/PropertyInject.20failure.20in.20CxfConfigurer]
> If you use @PropertyInject like:
> {code:java}
> public class Foo {
> @PropertyInject(value = "1")
> private Integer bar;
> }
> {code}
> Then you get an exception like:
> {code:java}
> java.lang.UnsupportedOperationException: Cannot inject value of class: class
> java.lang.Integer into: private java.lang.Integer
> {code}
> The original exception is swallowed, but it's something like:
> {code:java}
> IllegalArgumentException: Can not set java.lang.Integer field to int(1)
> {code}
> You can't use Field.setInt etc where the field type is not a primitive. You
> have to use Field.set in that case.
> [https://docs.oracle.com/javase/tutorial/reflect/member/fieldTrouble.html]
> Maybe it's related to this change:
> [https://github.com/apache/camel/commit/df19aec009164ba821c60518651dfc5eda3aee7d]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20700) camel-core: ReflectionHelper.setField may fail for numeric type fields
[
https://issues.apache.org/jira/browse/CAMEL-20700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20700:
Fix Version/s: 4.6.0
> camel-core: ReflectionHelper.setField may fail for numeric type fields
> --
>
> Key: CAMEL-20700
> URL: https://issues.apache.org/jira/browse/CAMEL-20700
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.3.0, 4.4.0, 4.5.0
>Reporter: James Netherton
>Priority: Minor
> Fix For: 4.6.0
>
>
> Originally reported here:
> [https://camel.zulipchat.com/#narrow/stream/257302-camel-quarkus/topic/PropertyInject.20failure.20in.20CxfConfigurer]
> If you use @PropertyInject like:
> {code:java}
> public class Foo {
> @PropertyInject(value = "1")
> private Integer bar;
> }
> {code}
> Then you get an exception like:
> {code:java}
> java.lang.UnsupportedOperationException: Cannot inject value of class: class
> java.lang.Integer into: private java.lang.Integer
> {code}
> The original exception is swallowed, but it's something like:
> {code:java}
> IllegalArgumentException: Can not set java.lang.Integer field to int(1)
> {code}
> You can't use Field.setInt etc where the field type is not a primitive. You
> have to use Field.set in that case.
> [https://docs.oracle.com/javase/tutorial/reflect/member/fieldTrouble.html]
> Maybe it's related to this change:
> [https://github.com/apache/camel/commit/df19aec009164ba821c60518651dfc5eda3aee7d]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20712) Exception not thrown in MessagePredicate line 62
[
https://issues.apache.org/jira/browse/CAMEL-20712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17840785#comment-17840785
]
Claus Ibsen commented on CAMEL-20712:
-
Yes it should throw
> Exception not thrown in MessagePredicate line 62
>
>
> Key: CAMEL-20712
> URL: https://issues.apache.org/jira/browse/CAMEL-20712
> Project: Camel
> Issue Type: Bug
> Components: camel-quickfix
>Reporter: Dmitrii Kriukov
>Assignee: Dmitrii Kriukov
>Priority: Major
>
> RuntimeCamelException.wrapRuntimeCamelException(e){color:#cc7832};{color}
> If it's expected to throw it, please let me know - I will create a PR
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20712) camel-quickfix - Exception not thrown in MessagePredicate line 62
[
https://issues.apache.org/jira/browse/CAMEL-20712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20712:
Summary: camel-quickfix - Exception not thrown in MessagePredicate line 62
(was: Exception not thrown in MessagePredicate line 62)
> camel-quickfix - Exception not thrown in MessagePredicate line 62
> -
>
> Key: CAMEL-20712
> URL: https://issues.apache.org/jira/browse/CAMEL-20712
> Project: Camel
> Issue Type: Bug
> Components: camel-quickfix
>Reporter: Dmitrii Kriukov
>Assignee: Dmitrii Kriukov
>Priority: Minor
>
> RuntimeCamelException.wrapRuntimeCamelException(e){color:#cc7832};{color}
> If it's expected to throw it, please let me know - I will create a PR
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20712) Exception not thrown in MessagePredicate line 62
[
https://issues.apache.org/jira/browse/CAMEL-20712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20712:
Priority: Minor (was: Major)
> Exception not thrown in MessagePredicate line 62
>
>
> Key: CAMEL-20712
> URL: https://issues.apache.org/jira/browse/CAMEL-20712
> Project: Camel
> Issue Type: Bug
> Components: camel-quickfix
>Reporter: Dmitrii Kriukov
>Assignee: Dmitrii Kriukov
>Priority: Minor
>
> RuntimeCamelException.wrapRuntimeCamelException(e){color:#cc7832};{color}
> If it's expected to throw it, please let me know - I will create a PR
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20711) compare() method of EipOptionComparator doesn't return 0 for equal elements
[ https://issues.apache.org/jira/browse/CAMEL-20711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20711. - Resolution: Not A Bug > compare() method of EipOptionComparator doesn't return 0 for equal elements > --- > > Key: CAMEL-20711 > URL: https://issues.apache.org/jira/browse/CAMEL-20711 > Project: Camel > Issue Type: Bug > Components: tooling >Reporter: Dmitrii Kriukov >Priority: Major > > Line 1519 > If it's expected, it's good to have a comment -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20704) Duplicate case branch in ExpressionDeserializers
[
https://issues.apache.org/jira/browse/CAMEL-20704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20704.
-
Resolution: Won't Do
> Duplicate case branch in ExpressionDeserializers
>
>
> Key: CAMEL-20704
> URL: https://issues.apache.org/jira/browse/CAMEL-20704
> Project: Camel
> Issue Type: Task
> Components: camel-yaml-dsl
>Reporter: Dmitrii Kriukov
>Assignee: Dmitrii Kriukov
>Priority: Minor
>
> case "expression-type":
> { return constructExpressionType(node); }
> case "expressionType": \{ return constructExpressionType(node); }
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20714) SourceCache implements Externalizable but doesn't have a public no-arg constructor
[ https://issues.apache.org/jira/browse/CAMEL-20714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20714. - Fix Version/s: 4.6.0 Resolution: Fixed > SourceCache implements Externalizable but doesn't have a public no-arg > constructor > -- > > Key: CAMEL-20714 > URL: https://issues.apache.org/jira/browse/CAMEL-20714 > Project: Camel > Issue Type: Task > Components: came-core >Reporter: Dmitrii Kriukov >Assignee: Dmitrii Kriukov >Priority: Minor > Fix For: 4.6.0 > > > Class org.apache.camel.util.xml.SourceCache -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20714) SourceCache implements Externalizable but doesn't have a public no-arg constructor
[ https://issues.apache.org/jira/browse/CAMEL-20714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20714: Issue Type: Task (was: Bug) > SourceCache implements Externalizable but doesn't have a public no-arg > constructor > -- > > Key: CAMEL-20714 > URL: https://issues.apache.org/jira/browse/CAMEL-20714 > Project: Camel > Issue Type: Task > Components: came-core >Reporter: Dmitrii Kriukov >Assignee: Dmitrii Kriukov >Priority: Major > > Class org.apache.camel.util.xml.SourceCache -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20714) SourceCache implements Externalizable but doesn't have a public no-arg constructor
[ https://issues.apache.org/jira/browse/CAMEL-20714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20714: Priority: Minor (was: Major) > SourceCache implements Externalizable but doesn't have a public no-arg > constructor > -- > > Key: CAMEL-20714 > URL: https://issues.apache.org/jira/browse/CAMEL-20714 > Project: Camel > Issue Type: Task > Components: came-core >Reporter: Dmitrii Kriukov >Assignee: Dmitrii Kriukov >Priority: Minor > > Class org.apache.camel.util.xml.SourceCache -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20715) camel-olingo2 and 4 - ApiName DEFAULT should be accepted
[ https://issues.apache.org/jira/browse/CAMEL-20715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20715. - Resolution: Fixed > camel-olingo2 and 4 - ApiName DEFAULT should be accepted > > > Key: CAMEL-20715 > URL: https://issues.apache.org/jira/browse/CAMEL-20715 > Project: Camel > Issue Type: Bug > Components: camel-olingo2, camel-olingo4 >Affects Versions: 4.4.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.4.3, 4.6.0 > > > Tooling such as Karavan and Kaoto would generate endpoints with DEFAULT as > the apiName which should be supported in the component > https://github.com/apache/camel-karavan/issues/1244 -- This message was sent by Atlassian Jira (v8.20.10#820010)
