[jira] [Resolved] (CAMEL-20734) Aws-xray: bump of aws-xray-recorder-sdk-bom brought conflict in dependencies
[
https://issues.apache.org/jira/browse/CAMEL-20734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20734.
-
Resolution: Fixed
> Aws-xray: bump of aws-xray-recorder-sdk-bom brought conflict in dependencies
> -
>
> Key: CAMEL-20734
> URL: https://issues.apache.org/jira/browse/CAMEL-20734
> Project: Camel
> Issue Type: Dependency upgrade
> Components: camel-aws-xray
>Affects Versions: 4.6.0
>Reporter: Jiri Ondrusek
>Assignee: Jiri Ondrusek
>Priority: Minor
> Fix For: 4.6.0
>
>
> I noticed (during build of camel-quarkus) that the bump of
> aws-xray-recorder-sdk-bom ([PR|https://github.com/apache/camel/pull/14016])
> brought conflict of _com.amazonaws:aws-java-sdk-core:jar_
>
> Bumped BOM brought aws-java-sdk-core in versions *.228* and *.708*
> {code:java}
> +-org.apache.camel:camel-aws-xray:4.6.0-SNAPSHOT
> +-com.amazonaws:aws-xray-recorder-sdk-aws-sdk:2.15.3
> +-com.amazonaws:aws-java-sdk-core:1.12.708
> {code}
> and
> {code:java}
> +-org.apache.camel:camel-aws-xray:4.6.0-SNAPSHOT
> +-com.amazonaws:aws-xray-recorder-sdk-core:2.15.3
> +-com.amazonaws:aws-java-sdk-xray:1.12.228
> +-com.amazonaws:aws-java-sdk-core:1.12.228 {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20734) Aws-xray: bump of aws-xray-recorder-sdk-bom brought conflict in dependencies
[
https://issues.apache.org/jira/browse/CAMEL-20734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20734:
Fix Version/s: 4.6.0
> Aws-xray: bump of aws-xray-recorder-sdk-bom brought conflict in dependencies
> -
>
> Key: CAMEL-20734
> URL: https://issues.apache.org/jira/browse/CAMEL-20734
> Project: Camel
> Issue Type: Dependency upgrade
> Components: camel-aws-xray
>Affects Versions: 4.6.0
>Reporter: Jiri Ondrusek
>Assignee: Jiri Ondrusek
>Priority: Minor
> Fix For: 4.6.0
>
>
> I noticed (during build of camel-quarkus) that the bump of
> aws-xray-recorder-sdk-bom ([PR|https://github.com/apache/camel/pull/14016])
> brought conflict of _com.amazonaws:aws-java-sdk-core:jar_
>
> Bumped BOM brought aws-java-sdk-core in versions *.228* and *.708*
> {code:java}
> +-org.apache.camel:camel-aws-xray:4.6.0-SNAPSHOT
> +-com.amazonaws:aws-xray-recorder-sdk-aws-sdk:2.15.3
> +-com.amazonaws:aws-java-sdk-core:1.12.708
> {code}
> and
> {code:java}
> +-org.apache.camel:camel-aws-xray:4.6.0-SNAPSHOT
> +-com.amazonaws:aws-xray-recorder-sdk-core:2.15.3
> +-com.amazonaws:aws-java-sdk-xray:1.12.228
> +-com.amazonaws:aws-java-sdk-core:1.12.228 {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20734) Aws-xray: bump of aws-xray-recorder-sdk-bom brought conflict in dependencies
[
https://issues.apache.org/jira/browse/CAMEL-20734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20734:
Issue Type: Dependency upgrade (was: Bug)
> Aws-xray: bump of aws-xray-recorder-sdk-bom brought conflict in dependencies
> -
>
> Key: CAMEL-20734
> URL: https://issues.apache.org/jira/browse/CAMEL-20734
> Project: Camel
> Issue Type: Dependency upgrade
> Components: camel-aws-xray
>Affects Versions: 4.6.0
>Reporter: Jiri Ondrusek
>Assignee: Jiri Ondrusek
>Priority: Major
>
> I noticed (during build of camel-quarkus) that the bump of
> aws-xray-recorder-sdk-bom ([PR|https://github.com/apache/camel/pull/14016])
> brought conflict of _com.amazonaws:aws-java-sdk-core:jar_
>
> Bumped BOM brought aws-java-sdk-core in versions *.228* and *.708*
> {code:java}
> +-org.apache.camel:camel-aws-xray:4.6.0-SNAPSHOT
> +-com.amazonaws:aws-xray-recorder-sdk-aws-sdk:2.15.3
> +-com.amazonaws:aws-java-sdk-core:1.12.708
> {code}
> and
> {code:java}
> +-org.apache.camel:camel-aws-xray:4.6.0-SNAPSHOT
> +-com.amazonaws:aws-xray-recorder-sdk-core:2.15.3
> +-com.amazonaws:aws-java-sdk-xray:1.12.228
> +-com.amazonaws:aws-java-sdk-core:1.12.228 {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20734) Aws-xray: bump of aws-xray-recorder-sdk-bom brought conflict in dependencies
[
https://issues.apache.org/jira/browse/CAMEL-20734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20734:
Priority: Minor (was: Major)
> Aws-xray: bump of aws-xray-recorder-sdk-bom brought conflict in dependencies
> -
>
> Key: CAMEL-20734
> URL: https://issues.apache.org/jira/browse/CAMEL-20734
> Project: Camel
> Issue Type: Dependency upgrade
> Components: camel-aws-xray
>Affects Versions: 4.6.0
>Reporter: Jiri Ondrusek
>Assignee: Jiri Ondrusek
>Priority: Minor
>
> I noticed (during build of camel-quarkus) that the bump of
> aws-xray-recorder-sdk-bom ([PR|https://github.com/apache/camel/pull/14016])
> brought conflict of _com.amazonaws:aws-java-sdk-core:jar_
>
> Bumped BOM brought aws-java-sdk-core in versions *.228* and *.708*
> {code:java}
> +-org.apache.camel:camel-aws-xray:4.6.0-SNAPSHOT
> +-com.amazonaws:aws-xray-recorder-sdk-aws-sdk:2.15.3
> +-com.amazonaws:aws-java-sdk-core:1.12.708
> {code}
> and
> {code:java}
> +-org.apache.camel:camel-aws-xray:4.6.0-SNAPSHOT
> +-com.amazonaws:aws-xray-recorder-sdk-core:2.15.3
> +-com.amazonaws:aws-java-sdk-xray:1.12.228
> +-com.amazonaws:aws-java-sdk-core:1.12.228 {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20734) Aws-xray: bump of aws-xray-recorder-sdk-bom brought conflict in dependencies
Jiri Ondrusek created CAMEL-20734:
-
Summary: Aws-xray: bump of aws-xray-recorder-sdk-bom brought
conflict in dependencies
Key: CAMEL-20734
URL: https://issues.apache.org/jira/browse/CAMEL-20734
Project: Camel
Issue Type: Bug
Components: camel-aws-xray
Affects Versions: 4.6.0
Reporter: Jiri Ondrusek
Assignee: Jiri Ondrusek
I noticed (during build of camel-quarkus) that the bump of
aws-xray-recorder-sdk-bom ([PR|https://github.com/apache/camel/pull/14016])
brought conflict of _com.amazonaws:aws-java-sdk-core:jar_
Bumped BOM brought aws-java-sdk-core in versions *.228* and *.708*
{code:java}
+-org.apache.camel:camel-aws-xray:4.6.0-SNAPSHOT
+-com.amazonaws:aws-xray-recorder-sdk-aws-sdk:2.15.3
+-com.amazonaws:aws-java-sdk-core:1.12.708
{code}
and
{code:java}
+-org.apache.camel:camel-aws-xray:4.6.0-SNAPSHOT
+-com.amazonaws:aws-xray-recorder-sdk-core:2.15.3
+-com.amazonaws:aws-java-sdk-xray:1.12.228
+-com.amazonaws:aws-java-sdk-core:1.12.228 {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[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] [Commented] (CAMEL-20653) kotlin-dsl: flaky build due to Kotlin DSL
[
https://issues.apache.org/jira/browse/CAMEL-20653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843170#comment-17843170
]
Otavio Rodolfo Piske commented on CAMEL-20653:
--
For some time the problem went away, but now I seem to get this error reliably.
It's a very annoying one as I have to restart the build (or then build only the
DSLs because of this).
> kotlin-dsl: flaky build due to Kotlin DSL
> -
>
> Key: CAMEL-20653
> URL: https://issues.apache.org/jira/browse/CAMEL-20653
> Project: Camel
> Issue Type: Task
> Components: build system, dsl
>Affects Versions: 4.6.0
>Reporter: Otavio Rodolfo Piske
>Priority: Major
> Fix For: 4.x
>
>
> Builds with Maven Daemon seem to fail quite often due to Kotlin issues such
> as:
>
> {code:java}
> [ERROR] Failed to execute goal
> org.jetbrains.kotlin:kotlin-maven-plugin:1.9.23:compile (compile) on project
> camel-kotlin-api: Compilation failure
> [ERROR] java.lang.RuntimeException: Could not find installation home path.
> Please make sure bin/idea.properties is present in the installation directory.
> {code}
>
> Trying to build it with maven seems to work OK.
--
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)
