[jira] [Created] (CAMEL-21400) StackOverflowError when processing files
Antoine DESSAIGNE created CAMEL-21400:
-
Summary: StackOverflowError when processing files
Key: CAMEL-21400
URL: https://issues.apache.org/jira/browse/CAMEL-21400
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 4.7.0
Reporter: Antoine DESSAIGNE
Hello everyone,
I just discovered a {{StackOverflowError}} when using reading files. Here's the
smallest reprocase I could find.
{code:java}
// Create a temp directory with a CSV file
Path tempDirectory = Files.createTempDirectory("camel-test");
try (BufferedWriter writer =
Files.newBufferedWriter(tempDirectory.resolve("file1.csv"))) {
writer.write("fieldA,fieldB,fieldC,fieldD\n");
for (int i = 0; i < 2; i++) {
writer.write("fieldA" + i + ",fieldB" + i + ",fieldC" + i + ",fieldD" +
i + "\n");
}
}
// Seems to fail if the target producer extends DefaultProducer and works if it
extends DefaultAsyncProducer
String target = "file://output"; // this fails
//String target = "log://speed?groupSize=1000"; // this works
DefaultCamelContext context = new DefaultCamelContext();
context.addRoutes(new RouteBuilder() {
@Override
public void configure() {
from("file://" + tempDirectory.toAbsolutePath() +
"?noop=true").to("direct:read").log("Done!");
from("direct:read").unmarshal().csv().split(body()).to("direct:agg");
from("direct:agg").aggregate(constant("SINGLE_GROUP"), new
GroupedExchangeAggregationStrategy())
.completionSize(1)
.setBody((Exchange exchange) -> {
List list = (List)
exchange.getMessage().getBody();
return list.stream().map(e ->
e.getMessage().getBody().toString()).collect(joining("\n"));
})
.to(target);
}
});
context.start();
{code}
As mentioned in the example, it only seems to fail if the processor in the
aggregation is a {{DefaultProcessor}} and not a {{DefaultAsyncProcessor}}.
Can you have a look? Thank you
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21391) camel-core - Add configuring dataFormats into model DSL
[
https://issues.apache.org/jira/browse/CAMEL-21391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17893732#comment-17893732
]
Claus Ibsen edited comment on CAMEL-21391 at 10/29/24 12:25 PM:
TODO: xml-io-dsl *DONE*
TODO: yaml-dsl *DONE*
TODO: xml io dumper
TODO: yaml dumper *DONE*
was (Author: davsclaus):
TODO: xml-io-dsl *DONE*
TODO: yaml-dsl *DONE*
TODO: xml io dumper
TODO: yaml dumper
> camel-core - Add configuring dataFormats into model DSL
> ---
>
> Key: CAMEL-21391
> URL: https://issues.apache.org/jira/browse/CAMEL-21391
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.9.0
>
>
> In the old OSGi blueprint/spring xml via they had special support for
> configuring data formats globally in . This is not in the DSL
> model of camel-core.
>
> We could considering add this, so its out of the box in xml-io and yaml DSL
> as well.
> However you would then refer to these global dataformats using ref="xxx"> style such as:
>
> {code:java}
> factory-method="getAESKey" />
> factory-method="getIV" />
> factory-method="getGCMParameterSpec" />
> http://camel.apache.org/schema/spring";>
>
> keyRef="aesKey" algorithmParameterRef="gcmParamSpec" />
>
>
>
> Hello Camel from ${routeId}
>
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-21396) Introduce a fury format
Zheng Feng created CAMEL-21396: -- Summary: Introduce a fury format Key: CAMEL-21396 URL: https://issues.apache.org/jira/browse/CAMEL-21396 Project: Camel Issue Type: New Feature Reporter: Zheng Feng Assignee: Zheng Feng Fix For: 4.9.0 Apache [Fury|https://fury.apache.org] (incubating) is a blazingly-fast multi-language serialization framework powered by JIT (just-in-time compilation) and zero-copy -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21397) camel-file: autoCreateStepwise not working in Windows
Sven created CAMEL-21397: Summary: camel-file: autoCreateStepwise not working in Windows Key: CAMEL-21397 URL: https://issues.apache.org/jira/browse/CAMEL-21397 Project: Camel Issue Type: Bug Components: camel-file Affects Versions: 4.8.1 Reporter: Sven 2 issues were found when testing this new feature on Windows with SMB shares: * When autoCreateStepWise is enabled it will always try to set permissions on the folder which fails as it's using Posix which throws UnsupportedOperationException * The path split is incorrect for as it does not take into account the SMB servername in the URI. It seems this part of the code was never foreseen to work for Windows style paths as it was only executed when permissions were set (which only works in Unix). In short: enabling autoCreateStepwise will always fail to create files on Windows environments (SMB or not). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21397) camel-file: autoCreateStepwise not working in Windows
[ https://issues.apache.org/jira/browse/CAMEL-21397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21397: Fix Version/s: 4.8.2 4.9.0 > camel-file: autoCreateStepwise not working in Windows > - > > Key: CAMEL-21397 > URL: https://issues.apache.org/jira/browse/CAMEL-21397 > Project: Camel > Issue Type: Bug > Components: camel-file >Affects Versions: 4.8.1 >Reporter: Sven >Priority: Minor > Fix For: 4.8.2, 4.9.0 > > > 2 issues were found when testing this new feature on Windows with SMB shares: > * When autoCreateStepWise is enabled it will always try to set permissions > on the folder which fails as it's using Posix which throws > UnsupportedOperationException > * The path split is incorrect for as it does not take into account the SMB > servername in the URI. It seems this part of the code was never foreseen to > work for Windows style paths as it was only executed when permissions were > set (which only works in Unix). > In short: enabling autoCreateStepwise will always fail to create files on > Windows environments (SMB or not). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21397) camel-file: autoCreateStepwise not working in Windows
[ https://issues.apache.org/jira/browse/CAMEL-21397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21397: Priority: Minor (was: Critical) > camel-file: autoCreateStepwise not working in Windows > - > > Key: CAMEL-21397 > URL: https://issues.apache.org/jira/browse/CAMEL-21397 > Project: Camel > Issue Type: Bug > Components: camel-file >Affects Versions: 4.8.1 >Reporter: Sven >Priority: Minor > > 2 issues were found when testing this new feature on Windows with SMB shares: > * When autoCreateStepWise is enabled it will always try to set permissions > on the folder which fails as it's using Posix which throws > UnsupportedOperationException > * The path split is incorrect for as it does not take into account the SMB > servername in the URI. It seems this part of the code was never foreseen to > work for Windows style paths as it was only executed when permissions were > set (which only works in Unix). > In short: enabling autoCreateStepwise will always fail to create files on > Windows environments (SMB or not). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21399) Kubernetes plugin regression. Fails on OCP deployments
[
https://issues.apache.org/jira/browse/CAMEL-21399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21399:
Fix Version/s: 4.8.2
4.9.0
> Kubernetes plugin regression. Fails on OCP deployments
> --
>
> Key: CAMEL-21399
> URL: https://issues.apache.org/jira/browse/CAMEL-21399
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.1
>Reporter: Bruno Meseguer
>Priority: Minor
> Fix For: 4.8.2, 4.9.0
>
>
> All seems to work well in 4.8.0
> Operating the same commands using 4.8.1 fails.
>
> Create a Camel route, for example, with:
> {code:java}
> camel init myroute.camel.yaml{code}
>
> Then using the commands below to deploy on OpenShift (tested in Developer
> Sandbox) run
>
> {code:java}
> camel version
> JBang version: 0.119.0
> Camel JBang version: 4.8.1
> camel kubernetes run * --cluster-type=openshift --dev
> {code}
>
>
> The execution fails with:
> {code:java}
> Run: kubectl get pod -l app.kubernetes.io/name=test
> Exception in thread "main" java.util.ServiceConfigurationError:
> io.fabric8.kubernetes.api.model.KubernetesResource:
> io.fabric8.kubernetes.api.model.LimitRange not a subtype{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21399) Kubernetes plugin regression. Fails on OCP deployments
[
https://issues.apache.org/jira/browse/CAMEL-21399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21399:
Summary: Kubernetes plugin regression. Fails on OCP deployments (was:
Kubernetes plugin regression. Fails on deployments)
> Kubernetes plugin regression. Fails on OCP deployments
> --
>
> Key: CAMEL-21399
> URL: https://issues.apache.org/jira/browse/CAMEL-21399
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.1
>Reporter: Bruno Meseguer
>Priority: Minor
>
> All seems to work well in 4.8.0
> Operating the same commands using 4.8.1 fails.
>
> Create a Camel route, for example, with:
> {code:java}
> camel init myroute.camel.yaml{code}
>
> Then using the commands below to deploy on OpenShift (tested in Developer
> Sandbox) run
>
> {code:java}
> camel version
> JBang version: 0.119.0
> Camel JBang version: 4.8.1
> camel kubernetes run * --cluster-type=openshift --dev
> {code}
>
>
> The execution fails with:
> {code:java}
> Run: kubectl get pod -l app.kubernetes.io/name=test
> Exception in thread "main" java.util.ServiceConfigurationError:
> io.fabric8.kubernetes.api.model.KubernetesResource:
> io.fabric8.kubernetes.api.model.LimitRange not a subtype{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21399) Kubernetes plugin regression. Fails on deployments
[
https://issues.apache.org/jira/browse/CAMEL-21399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17893780#comment-17893780
]
Claus Ibsen commented on CAMEL-21399:
-
Yeah that IntRange has been reported before, try with 4.9 SNAPSHOT
> Kubernetes plugin regression. Fails on deployments
> --
>
> Key: CAMEL-21399
> URL: https://issues.apache.org/jira/browse/CAMEL-21399
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.1
>Reporter: Bruno Meseguer
>Priority: Major
>
> All seems to work well in 4.8.0
> Operating the same commands using 4.8.1 fails.
>
> Create a Camel route, for example, with:
> {code:java}
> camel init myroute.camel.yaml{code}
>
> Then using the commands below to deploy on OpenShift (tested in Developer
> Sandbox) run
>
> {code:java}
> camel version
> JBang version: 0.119.0
> Camel JBang version: 4.8.1
> camel kubernetes run * --cluster-type=openshift --dev
> {code}
>
>
> The execution fails with:
> {code:java}
> Run: kubectl get pod -l app.kubernetes.io/name=test
> Exception in thread "main" java.util.ServiceConfigurationError:
> io.fabric8.kubernetes.api.model.KubernetesResource:
> io.fabric8.kubernetes.api.model.LimitRange not a subtype{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21399) Kubernetes plugin regression. Fails on deployments
[
https://issues.apache.org/jira/browse/CAMEL-21399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21399:
Priority: Minor (was: Major)
> Kubernetes plugin regression. Fails on deployments
> --
>
> Key: CAMEL-21399
> URL: https://issues.apache.org/jira/browse/CAMEL-21399
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.1
>Reporter: Bruno Meseguer
>Priority: Minor
>
> All seems to work well in 4.8.0
> Operating the same commands using 4.8.1 fails.
>
> Create a Camel route, for example, with:
> {code:java}
> camel init myroute.camel.yaml{code}
>
> Then using the commands below to deploy on OpenShift (tested in Developer
> Sandbox) run
>
> {code:java}
> camel version
> JBang version: 0.119.0
> Camel JBang version: 4.8.1
> camel kubernetes run * --cluster-type=openshift --dev
> {code}
>
>
> The execution fails with:
> {code:java}
> Run: kubectl get pod -l app.kubernetes.io/name=test
> Exception in thread "main" java.util.ServiceConfigurationError:
> io.fabric8.kubernetes.api.model.KubernetesResource:
> io.fabric8.kubernetes.api.model.LimitRange not a subtype{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21398) Smooks Data Format
[ https://issues.apache.org/jira/browse/CAMEL-21398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Mamo updated CAMEL-21398: Fix Version/s: 4.9.0 > Smooks Data Format > -- > > Key: CAMEL-21398 > URL: https://issues.apache.org/jira/browse/CAMEL-21398 > Project: Camel > Issue Type: New Feature >Reporter: Claude Mamo >Priority: Minor > Fix For: 4.9.0 > > > Migrate the Smooks Data Format from > [https://github.com/smooks/smooks-camel-cartridge/|https://github.com/smooks/smooks-camel-cartridge/issues/211] > to the Apache Camel code base (see > [https://github.com/smooks/smooks-camel-cartridge/issues/211]). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21398) Smooks Data Format
[ https://issues.apache.org/jira/browse/CAMEL-21398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Mamo updated CAMEL-21398: Labels: dataformat (was: ) > Smooks Data Format > -- > > Key: CAMEL-21398 > URL: https://issues.apache.org/jira/browse/CAMEL-21398 > Project: Camel > Issue Type: New Feature >Reporter: Claude Mamo >Priority: Minor > Labels: dataformat > Fix For: 4.9.0 > > > Migrate the Smooks Data Format from > [https://github.com/smooks/smooks-camel-cartridge/|https://github.com/smooks/smooks-camel-cartridge/issues/211] > to the Apache Camel code base (see > [https://github.com/smooks/smooks-camel-cartridge/issues/211]). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21391) camel-core - Add configuring dataFormats into model DSL
[
https://issues.apache.org/jira/browse/CAMEL-21391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17893732#comment-17893732
]
Claus Ibsen edited comment on CAMEL-21391 at 10/29/24 1:04 PM:
---
TODO: xml-io-dsl *DONE*
TODO: yaml-dsl *DONE*
TODO: xml io dumper *DONE*
TODO: xml jaxb dumper *DONE*
TODO: yaml dumper *DONE*
was (Author: davsclaus):
TODO: xml-io-dsl *DONE*
TODO: yaml-dsl *DONE*
TODO: xml io dumper
TODO: yaml dumper *DONE*
> camel-core - Add configuring dataFormats into model DSL
> ---
>
> Key: CAMEL-21391
> URL: https://issues.apache.org/jira/browse/CAMEL-21391
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.9.0
>
>
> In the old OSGi blueprint/spring xml via they had special support for
> configuring data formats globally in . This is not in the DSL
> model of camel-core.
>
> We could considering add this, so its out of the box in xml-io and yaml DSL
> as well.
> However you would then refer to these global dataformats using ref="xxx"> style such as:
>
> {code:java}
> factory-method="getAESKey" />
> factory-method="getIV" />
> factory-method="getGCMParameterSpec" />
> http://camel.apache.org/schema/spring";>
>
> keyRef="aesKey" algorithmParameterRef="gcmParamSpec" />
>
>
>
> Hello Camel from ${routeId}
>
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-21399) Kubernetes plugin regression. Fails on deployments
Bruno Meseguer created CAMEL-21399:
--
Summary: Kubernetes plugin regression. Fails on deployments
Key: CAMEL-21399
URL: https://issues.apache.org/jira/browse/CAMEL-21399
Project: Camel
Issue Type: Bug
Components: camel-jbang
Affects Versions: 4.8.1
Reporter: Bruno Meseguer
All seems to work well in 4.8.0
Operating the same commands using 4.8.1 fails.
Create a Camel route, for example, with:
{code:java}
camel init myroute.camel.yaml{code}
Then using the commands below to deploy on OpenShift (tested in Developer
Sandbox) run
{code:java}
camel version
JBang version: 0.119.0
Camel JBang version: 4.8.1
camel kubernetes run * --cluster-type=openshift --dev
{code}
The execution fails with:
{code:java}
Run: kubectl get pod -l app.kubernetes.io/name=test
Exception in thread "main" java.util.ServiceConfigurationError:
io.fabric8.kubernetes.api.model.KubernetesResource:
io.fabric8.kubernetes.api.model.LimitRange not a subtype{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21400) StackOverflowError when processing files
[
https://issues.apache.org/jira/browse/CAMEL-21400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21400:
Priority: Minor (was: Major)
> StackOverflowError when processing files
>
>
> Key: CAMEL-21400
> URL: https://issues.apache.org/jira/browse/CAMEL-21400
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.7.0
>Reporter: Antoine DESSAIGNE
>Priority: Minor
>
> Hello everyone,
> I just discovered a {{StackOverflowError}} when using reading files. Here's
> the smallest reprocase I could find.
> {code:java}
> // Create a temp directory with a CSV file
> Path tempDirectory = Files.createTempDirectory("camel-test");
> try (BufferedWriter writer =
> Files.newBufferedWriter(tempDirectory.resolve("file1.csv"))) {
> writer.write("fieldA,fieldB,fieldC,fieldD\n");
> for (int i = 0; i < 2; i++) {
> writer.write("fieldA" + i + ",fieldB" + i + ",fieldC" + i + ",fieldD"
> + i + "\n");
> }
> }
> // Seems to fail if the target producer extends DefaultProducer and works if
> it extends DefaultAsyncProducer
> String target = "file://output"; // this fails
> //String target = "log://speed?groupSize=1000"; // this works
> DefaultCamelContext context = new DefaultCamelContext();
> context.addRoutes(new RouteBuilder() {
> @Override
> public void configure() {
> from("file://" + tempDirectory.toAbsolutePath() +
> "?noop=true").to("direct:read").log("Done!");
> from("direct:read").unmarshal().csv().split(body()).to("direct:agg");
> from("direct:agg").aggregate(constant("SINGLE_GROUP"), new
> GroupedExchangeAggregationStrategy())
> .completionSize(1)
> .setBody((Exchange exchange) -> {
> List list = (List)
> exchange.getMessage().getBody();
> return list.stream().map(e ->
> e.getMessage().getBody().toString()).collect(joining("\n"));
> })
> .to(target);
> }
> });
> context.start();
> {code}
> As mentioned in the example, it only seems to fail if the processor in the
> aggregation is a {{DefaultProcessor}} and not a {{DefaultAsyncProcessor}}.
> Can you have a look? Thank you
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-21401) camel-core - Custom bean in DSL using factory method should avoid ClassCastException
Claus Ibsen created CAMEL-21401: --- Summary: camel-core - Custom bean in DSL using factory method should avoid ClassCastException Key: CAMEL-21401 URL: https://issues.apache.org/jira/browse/CAMEL-21401 Project: Camel Issue Type: Bug Components: camel-core Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 4.9.0 This can happen if custom beans are using factory-method and has not set a factory-class and uses the type name for that; which leads to ClassCastException as the result of the factory method can be any kind of Object. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21400) StackOverflowError when processing files
[
https://issues.apache.org/jira/browse/CAMEL-21400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17893936#comment-17893936
]
Antoine DESSAIGNE commented on CAMEL-21400:
---
Thanks to a git bisect, the regression is due to [commit
6324bc0a6da|https://github.com/apache/camel/commit/6324bc0a6dae05650b851a9524407c5382d3ff6e]
from CAMEL-16829
Unfortunately, I don't understand this part of the code. Please let me know if
there's anything I can do to help. Thank you.
> StackOverflowError when processing files
>
>
> Key: CAMEL-21400
> URL: https://issues.apache.org/jira/browse/CAMEL-21400
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.7.0
>Reporter: Antoine DESSAIGNE
>Priority: Minor
>
> Hello everyone,
> I just discovered a {{StackOverflowError}} when using reading files. Here's
> the smallest reprocase I could find.
> {code:java}
> // Create a temp directory with a CSV file
> Path tempDirectory = Files.createTempDirectory("camel-test");
> try (BufferedWriter writer =
> Files.newBufferedWriter(tempDirectory.resolve("file1.csv"))) {
> writer.write("fieldA,fieldB,fieldC,fieldD\n");
> for (int i = 0; i < 2; i++) {
> writer.write("fieldA" + i + ",fieldB" + i + ",fieldC" + i + ",fieldD"
> + i + "\n");
> }
> }
> // Seems to fail if the target producer extends DefaultProducer and works if
> it extends DefaultAsyncProducer
> String target = "file://output"; // this fails
> //String target = "log://speed?groupSize=1000"; // this works
> DefaultCamelContext context = new DefaultCamelContext();
> context.addRoutes(new RouteBuilder() {
> @Override
> public void configure() {
> from("file://" + tempDirectory.toAbsolutePath() +
> "?noop=true").to("direct:read").log("Done!");
> from("direct:read").unmarshal().csv().split(body()).to("direct:agg");
> from("direct:agg").aggregate(constant("SINGLE_GROUP"), new
> GroupedExchangeAggregationStrategy())
> .completionSize(1)
> .setBody((Exchange exchange) -> {
> List list = (List)
> exchange.getMessage().getBody();
> return list.stream().map(e ->
> e.getMessage().getBody().toString()).collect(joining("\n"));
> })
> .to(target);
> }
> });
> context.start();
> {code}
> -As mentioned in the example, it only seems to fail if the processor in the
> aggregation is a {{DefaultProcessor}} and not a {{DefaultAsyncProcessor}}-
> It still fails after converting my component to {{DefaultAsyncProcessor}}, so
> it's unrelated.
> Can you have a look? Thank you
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21401) camel-core - Custom bean in DSL using factory method should avoid ClassCastException
[ https://issues.apache.org/jira/browse/CAMEL-21401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17893934#comment-17893934 ] Claus Ibsen edited comment on CAMEL-21401 at 10/29/24 7:57 PM: --- TODO: backport fix to 4.8.x *DONE* was (Author: davsclaus): TODO: backport fix to 4.8.x > camel-core - Custom bean in DSL using factory method should avoid > ClassCastException > > > Key: CAMEL-21401 > URL: https://issues.apache.org/jira/browse/CAMEL-21401 > Project: Camel > Issue Type: Bug > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.8.2, 4.9.0 > > > This can happen if custom beans are using factory-method and has not set a > factory-class and uses the type name for that; which leads to > ClassCastException as the result of the factory method can be any kind of > Object. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21401) camel-core - Custom bean in DSL using factory method should avoid ClassCastException
[ https://issues.apache.org/jira/browse/CAMEL-21401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-21401. - Resolution: Fixed > camel-core - Custom bean in DSL using factory method should avoid > ClassCastException > > > Key: CAMEL-21401 > URL: https://issues.apache.org/jira/browse/CAMEL-21401 > Project: Camel > Issue Type: Bug > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.8.2, 4.9.0 > > > This can happen if custom beans are using factory-method and has not set a > factory-class and uses the type name for that; which leads to > ClassCastException as the result of the factory method can be any kind of > Object. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21402) Enhance Camel's testing capabilities of MockEndpoint with Expressions
Dmitrii Kriukov created CAMEL-21402: --- Summary: Enhance Camel's testing capabilities of MockEndpoint with Expressions Key: CAMEL-21402 URL: https://issues.apache.org/jira/browse/CAMEL-21402 Project: Camel Issue Type: Improvement Components: camel-mock Reporter: Dmitrii Kriukov Assignee: Dmitrii Kriukov My test case was: partially random value in an added header. It's difficult to test the exact value with existing API, so I was thinking about verifying against a regex. This option requires usage of Expressions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21278) Camel-Jbang Kubernetes Plugin: clean-up to new trait model and the tests
[ https://issues.apache.org/jira/browse/CAMEL-21278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaelle Fournier updated CAMEL-21278: Description: This is a follow-up from https://issues.apache.org/jira/browse/CAMEL-21152. Clean-up identified: * remove unused parameters and setters/getters * add some model builder * refactor the tests to improve the performance * move some trait specific code from KubernetesExport to the XxxTrait class was: This is a follow-up from https://issues.apache.org/jira/browse/CAMEL-21152. Clean-up identified: * remove unused parameters and setters/getters * add some model builder * refactor the tests to improve the performance > Camel-Jbang Kubernetes Plugin: clean-up to new trait model and the tests > > > Key: CAMEL-21278 > URL: https://issues.apache.org/jira/browse/CAMEL-21278 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Affects Versions: 4.x >Reporter: Gaelle Fournier >Assignee: Gaelle Fournier >Priority: Major > Fix For: 4.9.0 > > > This is a follow-up from https://issues.apache.org/jira/browse/CAMEL-21152. > Clean-up identified: > * remove unused parameters and setters/getters > * add some model builder > * refactor the tests to improve the performance > * move some trait specific code from KubernetesExport to the XxxTrait class -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21401) camel-core - Custom bean in DSL using factory method should avoid ClassCastException
[ https://issues.apache.org/jira/browse/CAMEL-21401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21401: Fix Version/s: 4.8.2 > camel-core - Custom bean in DSL using factory method should avoid > ClassCastException > > > Key: CAMEL-21401 > URL: https://issues.apache.org/jira/browse/CAMEL-21401 > Project: Camel > Issue Type: Bug > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.8.2, 4.9.0 > > > This can happen if custom beans are using factory-method and has not set a > factory-class and uses the type name for that; which leads to > ClassCastException as the result of the factory method can be any kind of > Object. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21369) camel-jbang - Kubernetes plugin - Use quarkus extensions for ingress and Route traits
[ https://issues.apache.org/jira/browse/CAMEL-21369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17893921#comment-17893921 ] Gaelle Fournier commented on CAMEL-21369: - The ingress generation will be excluded for now : [https://github.com/quarkusio/quarkus/issues/43783] > camel-jbang - Kubernetes plugin - Use quarkus extensions for ingress and > Route traits > - > > Key: CAMEL-21369 > URL: https://issues.apache.org/jira/browse/CAMEL-21369 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Affects Versions: 4.x >Reporter: Gaelle Fournier >Assignee: Gaelle Fournier >Priority: Major > Fix For: 4.9.0 > > > In Kubernetes plugin, Ingress and Route trait (service exposure) are only > available through the generated kubernetes/openshift manifest. > To leverage quarkus cloud readyness we should add for quarkus runtime cases > the use of: > * for ingress: > https://quarkus.io/guides/deploying-to-kubernetes#exposing-your-application-in-kubernetes > > * for openshift: > https://quarkus.io/guides/deploying-to-openshift#exposing_routes -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21369) camel-jbang - Kubernetes plugin - Use quarkus extensions for ingress and Route traits
[ https://issues.apache.org/jira/browse/CAMEL-21369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17893921#comment-17893921 ] Gaelle Fournier edited comment on CAMEL-21369 at 10/29/24 5:14 PM: --- The ingress generation will be excluded for now to another issue as it fails to be merged correctly: [https://github.com/quarkusio/quarkus/issues/43783] was (Author: JIRAUSER304516): The ingress generation will be excluded for now : [https://github.com/quarkusio/quarkus/issues/43783] > camel-jbang - Kubernetes plugin - Use quarkus extensions for ingress and > Route traits > - > > Key: CAMEL-21369 > URL: https://issues.apache.org/jira/browse/CAMEL-21369 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Affects Versions: 4.x >Reporter: Gaelle Fournier >Assignee: Gaelle Fournier >Priority: Major > Fix For: 4.9.0 > > > In Kubernetes plugin, Ingress and Route trait (service exposure) are only > available through the generated kubernetes/openshift manifest. > To leverage quarkus cloud readyness we should add for quarkus runtime cases > the use of: > * for ingress: > https://quarkus.io/guides/deploying-to-kubernetes#exposing-your-application-in-kubernetes > > * for openshift: > https://quarkus.io/guides/deploying-to-openshift#exposing_routes -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21400) StackOverflowError when processing files
[
https://issues.apache.org/jira/browse/CAMEL-21400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine DESSAIGNE updated CAMEL-21400:
--
Description:
Hello everyone,
I just discovered a {{StackOverflowError}} when using reading files. Here's the
smallest reprocase I could find.
{code:java}
// Create a temp directory with a CSV file
Path tempDirectory = Files.createTempDirectory("camel-test");
try (BufferedWriter writer =
Files.newBufferedWriter(tempDirectory.resolve("file1.csv"))) {
writer.write("fieldA,fieldB,fieldC,fieldD\n");
for (int i = 0; i < 2; i++) {
writer.write("fieldA" + i + ",fieldB" + i + ",fieldC" + i + ",fieldD" +
i + "\n");
}
}
// Seems to fail if the target producer extends DefaultProducer and works if it
extends DefaultAsyncProducer
String target = "file://output"; // this fails
//String target = "log://speed?groupSize=1000"; // this works
DefaultCamelContext context = new DefaultCamelContext();
context.addRoutes(new RouteBuilder() {
@Override
public void configure() {
from("file://" + tempDirectory.toAbsolutePath() +
"?noop=true").to("direct:read").log("Done!");
from("direct:read").unmarshal().csv().split(body()).to("direct:agg");
from("direct:agg").aggregate(constant("SINGLE_GROUP"), new
GroupedExchangeAggregationStrategy())
.completionSize(1)
.setBody((Exchange exchange) -> {
List list = (List)
exchange.getMessage().getBody();
return list.stream().map(e ->
e.getMessage().getBody().toString()).collect(joining("\n"));
})
.to(target);
}
});
context.start();
{code}
-As mentioned in the example, it only seems to fail if the processor in the
aggregation is a {{DefaultProcessor}} and not a {{DefaultAsyncProcessor}}-
It still fails after converting my component to {{DefaultAsyncProcessor}}, so
it's unrelated.
Can you have a look? Thank you
was:
Hello everyone,
I just discovered a {{StackOverflowError}} when using reading files. Here's the
smallest reprocase I could find.
{code:java}
// Create a temp directory with a CSV file
Path tempDirectory = Files.createTempDirectory("camel-test");
try (BufferedWriter writer =
Files.newBufferedWriter(tempDirectory.resolve("file1.csv"))) {
writer.write("fieldA,fieldB,fieldC,fieldD\n");
for (int i = 0; i < 2; i++) {
writer.write("fieldA" + i + ",fieldB" + i + ",fieldC" + i + ",fieldD" +
i + "\n");
}
}
// Seems to fail if the target producer extends DefaultProducer and works if it
extends DefaultAsyncProducer
String target = "file://output"; // this fails
//String target = "log://speed?groupSize=1000"; // this works
DefaultCamelContext context = new DefaultCamelContext();
context.addRoutes(new RouteBuilder() {
@Override
public void configure() {
from("file://" + tempDirectory.toAbsolutePath() +
"?noop=true").to("direct:read").log("Done!");
from("direct:read").unmarshal().csv().split(body()).to("direct:agg");
from("direct:agg").aggregate(constant("SINGLE_GROUP"), new
GroupedExchangeAggregationStrategy())
.completionSize(1)
.setBody((Exchange exchange) -> {
List list = (List)
exchange.getMessage().getBody();
return list.stream().map(e ->
e.getMessage().getBody().toString()).collect(joining("\n"));
})
.to(target);
}
});
context.start();
{code}
As mentioned in the example, it only seems to fail if the processor in the
aggregation is a {{DefaultProcessor}} and not a {{DefaultAsyncProcessor}}.
Can you have a look? Thank you
> StackOverflowError when processing files
>
>
> Key: CAMEL-21400
> URL: https://issues.apache.org/jira/browse/CAMEL-21400
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.7.0
>Reporter: Antoine DESSAIGNE
>Priority: Minor
>
> Hello everyone,
> I just discovered a {{StackOverflowError}} when using reading files. Here's
> the smallest reprocase I could find.
> {code:java}
> // Create a temp directory with a CSV file
> Path tempDirectory = Files.createTempDirectory("camel-test");
> try (BufferedWriter writer =
> Files.newBufferedWriter(tempDirectory.resolve("file1.csv"))) {
> writer.write("fieldA,fieldB,fieldC,fieldD\n");
> for (int i = 0; i < 2; i++) {
> writer.write("fieldA" + i + ",fieldB" + i + ",fieldC" + i + ",fieldD"
> + i + "\n");
> }
> }
> // Seems to fail if the target producer extends DefaultProducer and works if
> it extends DefaultAsyncProducer
> String target = "file://output"; // this fails
> //String target = "log://speed?groupSize=1000"; // this works
> DefaultCamelContext context = new DefaultCamelContext();
>
[jira] [Resolved] (CAMEL-21391) camel-core - Add configuring dataFormats into model DSL
[
https://issues.apache.org/jira/browse/CAMEL-21391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-21391.
-
Resolution: Fixed
> camel-core - Add configuring dataFormats into model DSL
> ---
>
> Key: CAMEL-21391
> URL: https://issues.apache.org/jira/browse/CAMEL-21391
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.9.0
>
>
> In the old OSGi blueprint/spring xml via they had special support for
> configuring data formats globally in . This is not in the DSL
> model of camel-core.
>
> We could considering add this, so its out of the box in xml-io and yaml DSL
> as well.
> However you would then refer to these global dataformats using ref="xxx"> style such as:
>
> {code:java}
> factory-method="getAESKey" />
> factory-method="getIV" />
> factory-method="getGCMParameterSpec" />
> http://camel.apache.org/schema/spring";>
>
> keyRef="aesKey" algorithmParameterRef="gcmParamSpec" />
>
>
>
> Hello Camel from ${routeId}
>
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21401) camel-core - Custom bean in DSL using factory method should avoid ClassCastException
[ https://issues.apache.org/jira/browse/CAMEL-21401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17893934#comment-17893934 ] Claus Ibsen commented on CAMEL-21401: - TODO: backport fix to 4.8.x > camel-core - Custom bean in DSL using factory method should avoid > ClassCastException > > > Key: CAMEL-21401 > URL: https://issues.apache.org/jira/browse/CAMEL-21401 > Project: Camel > Issue Type: Bug > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.9.0 > > > This can happen if custom beans are using factory-method and has not set a > factory-class and uses the type name for that; which leads to > ClassCastException as the result of the factory method can be any kind of > Object. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21369) camel-jbang - Kubernetes plugin - Use quarkus extensions for ingress and Route traits
[ https://issues.apache.org/jira/browse/CAMEL-21369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17891787#comment-17891787 ] Gaelle Fournier edited comment on CAMEL-21369 at 10/29/24 5:13 PM: --- Due to this issue the manifest is not available at the moment for openshift : https://issues.apache.org/jira/browse/CAMEL-21365 was (Author: JIRAUSER304516): Du to this issue the manifest is not available at the moment for openshift : https://issues.apache.org/jira/browse/CAMEL-21365 > camel-jbang - Kubernetes plugin - Use quarkus extensions for ingress and > Route traits > - > > Key: CAMEL-21369 > URL: https://issues.apache.org/jira/browse/CAMEL-21369 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Affects Versions: 4.x >Reporter: Gaelle Fournier >Assignee: Gaelle Fournier >Priority: Major > Fix For: 4.9.0 > > > In Kubernetes plugin, Ingress and Route trait (service exposure) are only > available through the generated kubernetes/openshift manifest. > To leverage quarkus cloud readyness we should add for quarkus runtime cases > the use of: > * for ingress: > https://quarkus.io/guides/deploying-to-kubernetes#exposing-your-application-in-kubernetes > > * for openshift: > https://quarkus.io/guides/deploying-to-openshift#exposing_routes -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21395) camel-debezium - Avoid split packages
[ https://issues.apache.org/jira/browse/CAMEL-21395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Filotto updated CAMEL-21395: Fix Version/s: 4.8.2 > camel-debezium - Avoid split packages > -- > > Key: CAMEL-21395 > URL: https://issues.apache.org/jira/browse/CAMEL-21395 > Project: Camel > Issue Type: Task > Components: camel-debezium >Affects Versions: 4.8.1 >Reporter: Nicolas Filotto >Assignee: Nicolas Filotto >Priority: Major > Fix For: 4.8.2, 4.9.0 > > > The project camel-debezium-common shares the same package with the other > camel-debezium sub-projects, which causes issues on environments like OSGI. > The goal of this task is to avoid the split packages issue -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21391) camel-core - Add configuring dataFormats into model DSL
[
https://issues.apache.org/jira/browse/CAMEL-21391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17893732#comment-17893732
]
Claus Ibsen commented on CAMEL-21391:
-
TODO: xml-io-dsl *DONE*
TODO: yaml-dsl *DONE*
TODO: xml io dumper
TODO: yaml dumper
> camel-core - Add configuring dataFormats into model DSL
> ---
>
> Key: CAMEL-21391
> URL: https://issues.apache.org/jira/browse/CAMEL-21391
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.9.0
>
>
> In the old OSGi blueprint/spring xml via they had special support for
> configuring data formats globally in . This is not in the DSL
> model of camel-core.
>
> We could considering add this, so its out of the box in xml-io and yaml DSL
> as well.
> However you would then refer to these global dataformats using ref="xxx"> style such as:
>
> {code:java}
> factory-method="getAESKey" />
> factory-method="getIV" />
> factory-method="getGCMParameterSpec" />
> http://camel.apache.org/schema/spring";>
>
> keyRef="aesKey" algorithmParameterRef="gcmParamSpec" />
>
>
>
> Hello Camel from ${routeId}
>
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21398) Smooks Data Format
[ https://issues.apache.org/jira/browse/CAMEL-21398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Mamo updated CAMEL-21398: Description: Migrate the Smooks Data Format from [https://github.com/smooks/smooks-camel-cartridge/|https://github.com/smooks/smooks-camel-cartridge/issues/211] to the Apache Camel code base (see [https://github.com/smooks/smooks-camel-cartridge/issues/211]). (was: Migrate the Smooks Data Format from [https://github.com/smooks/smooks-camel-cartridge/issues/211] to the Apache Camel code base (see https://github.com/smooks/smooks-camel-cartridge/issues/211).) > Smooks Data Format > -- > > Key: CAMEL-21398 > URL: https://issues.apache.org/jira/browse/CAMEL-21398 > Project: Camel > Issue Type: New Feature >Reporter: Claude Mamo >Priority: Minor > > Migrate the Smooks Data Format from > [https://github.com/smooks/smooks-camel-cartridge/|https://github.com/smooks/smooks-camel-cartridge/issues/211] > to the Apache Camel code base (see > [https://github.com/smooks/smooks-camel-cartridge/issues/211]). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21398) Smooks Data Format
Claude Mamo created CAMEL-21398: --- Summary: Smooks Data Format Key: CAMEL-21398 URL: https://issues.apache.org/jira/browse/CAMEL-21398 Project: Camel Issue Type: New Feature Reporter: Claude Mamo Migrate the Smooks Data Format from [https://github.com/smooks/smooks-camel-cartridge/issues/211] to the Apache Camel code base (see https://github.com/smooks/smooks-camel-cartridge/issues/211). -- This message was sent by Atlassian Jira (v8.20.10#820010)
