[jira] [Updated] (CAMEL-18170) Add serviceAccountKey parameter to google components
[
https://issues.apache.org/jira/browse/CAMEL-18170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18170:
Fix Version/s: 3.18.0
> Add serviceAccountKey parameter to google components
>
>
> Key: CAMEL-18170
> URL: https://issues.apache.org/jira/browse/CAMEL-18170
> Project: Camel
> Issue Type: Improvement
> Components: camel-google-calendar, camel-google-drive,
> camel-google-mail, camel-google-sheets
>Reporter: Claudio Miranda
>Assignee: Otavio Rodolfo Piske
>Priority: Minor
> Fix For: 3.18.0
>
>
> Add support to use {{service account key}} parameter to google components:
> sheets, calendar, mail, drive.
> Similar to google bigquery component.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Resolved] (CAMEL-18195) Add setExceptionListener(...) to SjmsComponent
[
https://issues.apache.org/jira/browse/CAMEL-18195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-18195.
-
Resolution: Fixed
> Add setExceptionListener(...) to SjmsComponent
> ---
>
> Key: CAMEL-18195
> URL: https://issues.apache.org/jira/browse/CAMEL-18195
> Project: Camel
> Issue Type: New Feature
> Components: camel-sjms
>Reporter: Lance S
>Priority: Minor
> Fix For: 3.18.0
>
>
> I'd like to set an exception listener for all topics using "sjms2" but
> SjmsComponent is missing a setExceptionListener(...) method
> [https://github.com/apache/camel/blob/main/components/camel-sjms/src/main/java/org/apache/camel/component/sjms/SjmsComponent.java]
>
> You can see that the "jms" component has a setExceptionListener(...) method
> but I don't want spring-jms on my classpath
> [https://github.com/apache/camel/blob/main/components/camel-jms/src/main/java/org/apache/camel/component/jms/JmsComponent.java#L331-L333]
>
> As a workaround I have the choice to:
> 1. Set the exception listener in the URI of every jms inbound adapter
> eg: "sjms2:some-topic?exceptionListener=#myExceptionListener"
>
> 2. Extend SjmsComponent2 to set the ExceptionListener on the Sjms2Component
> {code:java}
> ExceptionListener myExceptionListener = ex -> handleException(ex);
> Sjms2Component jmsComponent = new Sjms2Component() {
> protected SjmsEndpoint createSjmsEndpoint(String uri, String remaining) {
> SjmsEndpoint endpoint super.createSjmsEndpoint(uri, remaining);
> endpoint.setExceptionListener(exceptionListener);
> return endpoint;
> }
> }{code}
>
> I'd like to request that setExceptionListener(...) be added to SjmsComponent
> (which will be inherited by Sjms2Component)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (CAMEL-18195) Add setExceptionListener(...) to SjmsComponent
[
https://issues.apache.org/jira/browse/CAMEL-18195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18195:
Fix Version/s: 3.18.0
> Add setExceptionListener(...) to SjmsComponent
> ---
>
> Key: CAMEL-18195
> URL: https://issues.apache.org/jira/browse/CAMEL-18195
> Project: Camel
> Issue Type: New Feature
> Components: camel-sjms
>Reporter: Lance S
>Priority: Minor
> Fix For: 3.18.0
>
>
> I'd like to set an exception listener for all topics using "sjms2" but
> SjmsComponent is missing a setExceptionListener(...) method
> [https://github.com/apache/camel/blob/main/components/camel-sjms/src/main/java/org/apache/camel/component/sjms/SjmsComponent.java]
>
> You can see that the "jms" component has a setExceptionListener(...) method
> but I don't want spring-jms on my classpath
> [https://github.com/apache/camel/blob/main/components/camel-jms/src/main/java/org/apache/camel/component/jms/JmsComponent.java#L331-L333]
>
> As a workaround I have the choice to:
> 1. Set the exception listener in the URI of every jms inbound adapter
> eg: "sjms2:some-topic?exceptionListener=#myExceptionListener"
>
> 2. Extend SjmsComponent2 to set the ExceptionListener on the Sjms2Component
> {code:java}
> ExceptionListener myExceptionListener = ex -> handleException(ex);
> Sjms2Component jmsComponent = new Sjms2Component() {
> protected SjmsEndpoint createSjmsEndpoint(String uri, String remaining) {
> SjmsEndpoint endpoint super.createSjmsEndpoint(uri, remaining);
> endpoint.setExceptionListener(exceptionListener);
> return endpoint;
> }
> }{code}
>
> I'd like to request that setExceptionListener(...) be added to SjmsComponent
> (which will be inherited by Sjms2Component)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (CAMEL-18197) DocumentationEnricher uses deprecated api
Claus Ibsen created CAMEL-18197: --- Summary: DocumentationEnricher uses deprecated api Key: CAMEL-18197 URL: https://issues.apache.org/jira/browse/CAMEL-18197 Project: Camel Issue Type: Test Components: build system Reporter: Claus Ibsen Fix For: 3.x [WARNING] /Users/davsclaus/workspace/camel/tooling/maven/camel-eip-documentation-enricher-maven-plugin/src/main/java/org/apache/camel/maven/DocumentationEnricher.java:[147,24] [deprecation] WordUtils in org.apache.commons.lang3.text has been deprecated -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (CAMEL-18196) POJO-Producing: java.lang.IllegalStateException: Producer has not been started
[
https://issues.apache.org/jira/browse/CAMEL-18196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Url updated CAMEL-18196:
--
Component/s: documentation
> POJO-Producing: java.lang.IllegalStateException: Producer has not been started
> --
>
> Key: CAMEL-18196
> URL: https://issues.apache.org/jira/browse/CAMEL-18196
> Project: Camel
> Issue Type: Bug
> Components: camel-core, documentation
>Affects Versions: 3.17.0
>Reporter: David Url
>Priority: Major
>
> I was following the POJO-Producing seciton in the manual in order to have
> transport agnostic spring beans that produce events.
> (https://camel.apache.org/manual/pojo-producing.html#_hiding_the_camel_apis_from_your_code)
> My setup looks like this:
> {code}
> @Component
> public class RecorderSender {
>public static final String ENDPOINT_NAME =
> "direct:recorderSender?block=true=true";
>private ProducerEndpoint endpoint;
>@Produce(RecorderSender.ENDPOINT_NAME)
>public void setEndpoint(final ProducerEndpoint endpoint) {
> this.endpoint = endpoint;
>}
>public void write(final byte[] payload) {
> this.endpoint.send(payload);
>}
> }
> @InOnly
> public interface ProducerEndpoint {
>void send(T object);
> }
> {code}
> However once my spring bean is initialized it starts calling
> {{RecorderSender.write(byte[])}} at a time where the CamelContext is not yet
> initialized, and I get this exception:
> {noformat}
> Exception in thread "connector-1" java.lang.IllegalStateException: Producer
> has not been started:
> Producer[direct://recorderSender?block=true=true]
> at
> org.apache.camel.processor.EventNotifierProducer.process(EventNotifierProducer.java:54)
> at
> org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.process(DefaultAsyncProcessorAwaitManager.java:83)
> at
> org.apache.camel.support.DefaultAsyncProducer.process(DefaultAsyncProducer.java:41)
> at
> org.apache.camel.component.bean.AbstractCamelInvocationHandler$1.call(AbstractCamelInvocationHandler.java:189)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> org.apache.camel.component.bean.AbstractCamelInvocationHandler.doInvoke(AbstractCamelInvocationHandler.java:207)
> at
> org.apache.camel.component.bean.AbstractCamelInvocationHandler.invokeProxy(AbstractCamelInvocationHandler.java:169)
> at
> org.apache.camel.component.bean.CamelInvocationHandler.doInvokeProxy(CamelInvocationHandler.java:43)
> at
> org.apache.camel.component.bean.AbstractCamelInvocationHandler.invoke(AbstractCamelInvocationHandler.java:81)
> at jdk.proxy2/jdk.proxy2.$Proxy99.send(Unknown Source)
> at com.example.RecorderSender.write(RecorderSender.java:45)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at java.base/java.lang.Thread.run(Thread.java:833)
> {noformat}
> I assumed that the properties {{block}} and {{synchronous}} would ensure that
> the call is blocking, regardless of the initialization state of the
> CamelContext.
> I'm not sure whether this is actually a bug, or intentional behavior. But it
> would be nice to have the POJO Producing guide mentioning this behavior, or
> hinting at a better solution.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (CAMEL-18196) POJO-Producing: java.lang.IllegalStateException: Producer has not been started
David Url created CAMEL-18196:
-
Summary: POJO-Producing: java.lang.IllegalStateException: Producer
has not been started
Key: CAMEL-18196
URL: https://issues.apache.org/jira/browse/CAMEL-18196
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 3.17.0
Reporter: David Url
I was following the POJO-Producing seciton in the manual in order to have
transport agnostic spring beans that produce events.
(https://camel.apache.org/manual/pojo-producing.html#_hiding_the_camel_apis_from_your_code)
My setup looks like this:
{code}
@Component
public class RecorderSender {
public static final String ENDPOINT_NAME =
"direct:recorderSender?block=true=true";
private ProducerEndpoint endpoint;
@Produce(RecorderSender.ENDPOINT_NAME)
public void setEndpoint(final ProducerEndpoint endpoint) {
this.endpoint = endpoint;
}
public void write(final byte[] payload) {
this.endpoint.send(payload);
}
}
@InOnly
public interface ProducerEndpoint {
void send(T object);
}
{code}
However once my spring bean is initialized it starts calling
{{RecorderSender.write(byte[])}} at a time where the CamelContext is not yet
initialized, and I get this exception:
{noformat}
Exception in thread "connector-1" java.lang.IllegalStateException: Producer has
not been started: Producer[direct://recorderSender?block=true=true]
at
org.apache.camel.processor.EventNotifierProducer.process(EventNotifierProducer.java:54)
at
org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.process(DefaultAsyncProcessorAwaitManager.java:83)
at
org.apache.camel.support.DefaultAsyncProducer.process(DefaultAsyncProducer.java:41)
at
org.apache.camel.component.bean.AbstractCamelInvocationHandler$1.call(AbstractCamelInvocationHandler.java:189)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
org.apache.camel.component.bean.AbstractCamelInvocationHandler.doInvoke(AbstractCamelInvocationHandler.java:207)
at
org.apache.camel.component.bean.AbstractCamelInvocationHandler.invokeProxy(AbstractCamelInvocationHandler.java:169)
at
org.apache.camel.component.bean.CamelInvocationHandler.doInvokeProxy(CamelInvocationHandler.java:43)
at
org.apache.camel.component.bean.AbstractCamelInvocationHandler.invoke(AbstractCamelInvocationHandler.java:81)
at jdk.proxy2/jdk.proxy2.$Proxy99.send(Unknown Source)
at com.example.RecorderSender.write(RecorderSender.java:45)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:833)
{noformat}
I assumed that the properties {{block}} and {{synchronous}} would ensure that
the call is blocking, regardless of the initialization state of the
CamelContext.
I'm not sure whether this is actually a bug, or intentional behavior. But it
would be nice to have the POJO Producing guide mentioning this behavior, or
hinting at a better solution.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Resolved] (CAMEL-18176) Create a camel-hashicorp-vault test-infra module
[ https://issues.apache.org/jira/browse/CAMEL-18176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18176. -- Resolution: Fixed > Create a camel-hashicorp-vault test-infra module > > > Key: CAMEL-18176 > URL: https://issues.apache.org/jira/browse/CAMEL-18176 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.18.0 > > > To have a way to test the vault locally -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (CAMEL-18195) Add setExceptionListener(...) to SjmsComponent
[
https://issues.apache.org/jira/browse/CAMEL-18195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lance S updated CAMEL-18195:
Description:
I'd like to set an exception listener for all topics using "sjms2" but
SjmsComponent is missing a setExceptionListener(...) method
[https://github.com/apache/camel/blob/main/components/camel-sjms/src/main/java/org/apache/camel/component/sjms/SjmsComponent.java]
You can see that the "jms" component has a setExceptionListener(...) method but
I don't want spring-jms on my classpath
[https://github.com/apache/camel/blob/main/components/camel-jms/src/main/java/org/apache/camel/component/jms/JmsComponent.java#L331-L333]
As a workaround I have the choice to:
1. Set the exception listener in the URI of every jms inbound adapter
eg: "sjms2:some-topic?exceptionListener=#myExceptionListener"
2. Extend SjmsComponent2 to set the ExceptionListener on the Sjms2Component
{code:java}
ExceptionListener myExceptionListener = ex -> handleException(ex);
Sjms2Component jmsComponent = new Sjms2Component() {
protected SjmsEndpoint createSjmsEndpoint(String uri, String remaining) {
SjmsEndpoint endpoint super.createSjmsEndpoint(uri, remaining);
endpoint.setExceptionListener(exceptionListener);
return endpoint;
}
}{code}
I'd like to request that setExceptionListener(...) be added to SjmsComponent
(which will be inherited by Sjms2Component)
was:
I'd like to set an exception listener for all topics using "sjms2" but
SjmsComponent is missing a setExceptionListener(...) method
[https://github.com/apache/camel/blob/main/components/camel-sjms/src/main/java/org/apache/camel/component/sjms/SjmsComponent.java]
You can see that the "jms" component has a setExceptionListener(...) method but
I don't want spring-jms on my classpath
[https://github.com/apache/camel/blob/main/components/camel-jms/src/main/java/org/apache/camel/component/jms/JmsComponent.java#L331-L333]
As a workaround I have the choice to:
1. Set the exception listener in the URI of every jms inbound adapter
eg: "sjms2:some-topic?exceptionListener=#myExceptionListener"
2. Extend SjmsComponent2 to set the ExceptionListener on the Sjms2Component
{code:java}
ExceptionListener myExceptionListener = ex -> handleException(ex);
Sjms2Component jmsComponent = new Sjms2Component() {
protected SjmsEndpoint createSjmsEndpoint(String uri, String remaining) {
SjmsEndpoint endpoint super.createSjmsEndpoin(uri, remaining);
endpoint.setExceptionListener(exceptionListener);
return endpoint;
}
}{code}
I'd like to request that setExceptionListener(...) be added to SjmsComponent
(which will be inherited by Sjms2Component)
> Add setExceptionListener(...) to SjmsComponent
> ---
>
> Key: CAMEL-18195
> URL: https://issues.apache.org/jira/browse/CAMEL-18195
> Project: Camel
> Issue Type: New Feature
> Components: camel-sjms
>Reporter: Lance S
>Priority: Minor
>
> I'd like to set an exception listener for all topics using "sjms2" but
> SjmsComponent is missing a setExceptionListener(...) method
> [https://github.com/apache/camel/blob/main/components/camel-sjms/src/main/java/org/apache/camel/component/sjms/SjmsComponent.java]
>
> You can see that the "jms" component has a setExceptionListener(...) method
> but I don't want spring-jms on my classpath
> [https://github.com/apache/camel/blob/main/components/camel-jms/src/main/java/org/apache/camel/component/jms/JmsComponent.java#L331-L333]
>
> As a workaround I have the choice to:
> 1. Set the exception listener in the URI of every jms inbound adapter
> eg: "sjms2:some-topic?exceptionListener=#myExceptionListener"
>
> 2. Extend SjmsComponent2 to set the ExceptionListener on the Sjms2Component
> {code:java}
> ExceptionListener myExceptionListener = ex -> handleException(ex);
> Sjms2Component jmsComponent = new Sjms2Component() {
> protected SjmsEndpoint createSjmsEndpoint(String uri, String remaining) {
> SjmsEndpoint endpoint super.createSjmsEndpoint(uri, remaining);
> endpoint.setExceptionListener(exceptionListener);
> return endpoint;
> }
> }{code}
>
> I'd like to request that setExceptionListener(...) be added to SjmsComponent
> (which will be inherited by Sjms2Component)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (CAMEL-18195) Add setExceptionListener(...) to SjmsComponent
[
https://issues.apache.org/jira/browse/CAMEL-18195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lance S updated CAMEL-18195:
Description:
I'd like to set an exception listener for all topics using "sjms2" but
SjmsComponent is missing a setExceptionListener(...) method
[https://github.com/apache/camel/blob/main/components/camel-sjms/src/main/java/org/apache/camel/component/sjms/SjmsComponent.java]
You can see that the "jms" component has a setExceptionListener(...) method but
I don't want spring-jms on my classpath
[https://github.com/apache/camel/blob/main/components/camel-jms/src/main/java/org/apache/camel/component/jms/JmsComponent.java#L331-L333]
As a workaround I have the choice to:
1. Set the exception listener in the URI of every jms inbound adapter
eg: "sjms2:some-topic?exceptionListener=#myExceptionListener"
2. Extend SjmsComponent2 to set the ExceptionListener on the Sjms2Component
{code:java}
ExceptionListener myExceptionListener = ex -> handleException(ex);
Sjms2Component jmsComponent = new Sjms2Component() {
protected SjmsEndpoint createSjmsEndpoint(String uri, String remaining) {
SjmsEndpoint endpoint super.createSjmsEndpoin(uri, remaining);
endpoint.setExceptionListener(exceptionListener);
return endpoint;
}
}{code}
I'd like to request that setExceptionListener(...) be added to SjmsComponent
(which will be inherited by Sjms2Component)
was:
I'd like to set an exception listener for all topics using "sjms2" but
SjmsComponent is missing a setExceptionListener(...) method
[https://github.com/apache/camel/blob/main/components/camel-sjms/src/main/java/org/apache/camel/component/sjms/SjmsComponent.java]
You can see that the "jms" component has a setExceptionListener(...) method but
I don't want spring-jms on my classpath
[https://github.com/apache/camel/blob/main/components/camel-jms/src/main/java/org/apache/camel/component/jms/JmsComponent.java#L331-L333]
As a workaround I have the choice to:
1. Set the exception listener in the URI of every jms inbound adapter
eg: "sjms2:some-topic?exceptionListener=#myExceptionListener"
2. Extend SjmsComponent2 to set the ExceptionListener on the Sjms2Component
{code:java}
ExceptionListener myExceptionListener = ex -> handleException(ex);
Sjms2Component jmsComponent = new Sjms2Component() {
protected SjmsEndpoint createSjmsEndpoint(String uri, String remaining) {
SjmsEndpoint endpoint = new Sjms2Endpoint(uri, this, remaining);
endpoint.setExceptionListener(exceptionListener);
return endpoint;
}
}{code}
I'd like to request that setExceptionListener(...) be added to SjmsComponent
(which will be inherited by Sjms2Component)
> Add setExceptionListener(...) to SjmsComponent
> ---
>
> Key: CAMEL-18195
> URL: https://issues.apache.org/jira/browse/CAMEL-18195
> Project: Camel
> Issue Type: New Feature
> Components: camel-sjms
>Reporter: Lance S
>Priority: Minor
>
> I'd like to set an exception listener for all topics using "sjms2" but
> SjmsComponent is missing a setExceptionListener(...) method
> [https://github.com/apache/camel/blob/main/components/camel-sjms/src/main/java/org/apache/camel/component/sjms/SjmsComponent.java]
>
> You can see that the "jms" component has a setExceptionListener(...) method
> but I don't want spring-jms on my classpath
> [https://github.com/apache/camel/blob/main/components/camel-jms/src/main/java/org/apache/camel/component/jms/JmsComponent.java#L331-L333]
>
> As a workaround I have the choice to:
> 1. Set the exception listener in the URI of every jms inbound adapter
> eg: "sjms2:some-topic?exceptionListener=#myExceptionListener"
>
> 2. Extend SjmsComponent2 to set the ExceptionListener on the Sjms2Component
> {code:java}
> ExceptionListener myExceptionListener = ex -> handleException(ex);
> Sjms2Component jmsComponent = new Sjms2Component() {
> protected SjmsEndpoint createSjmsEndpoint(String uri, String remaining) {
> SjmsEndpoint endpoint super.createSjmsEndpoin(uri, remaining);
> endpoint.setExceptionListener(exceptionListener);
> return endpoint;
> }
> }{code}
>
> I'd like to request that setExceptionListener(...) be added to SjmsComponent
> (which will be inherited by Sjms2Component)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (CAMEL-18195) Add setExceptionListener(...) to SjmsComponent
Lance S created CAMEL-18195:
---
Summary: Add setExceptionListener(...) to SjmsComponent
Key: CAMEL-18195
URL: https://issues.apache.org/jira/browse/CAMEL-18195
Project: Camel
Issue Type: New Feature
Components: camel-sjms
Reporter: Lance S
I'd like to set an exception listener for all topics using "sjms2" but
SjmsComponent is missing a setExceptionListener(...) method
[https://github.com/apache/camel/blob/main/components/camel-sjms/src/main/java/org/apache/camel/component/sjms/SjmsComponent.java]
You can see that the "jms" component has a setExceptionListener(...) method but
I don't want spring-jms on my classpath
[https://github.com/apache/camel/blob/main/components/camel-jms/src/main/java/org/apache/camel/component/jms/JmsComponent.java#L331-L333]
As a workaround I have the choice to:
1. Set the exception listener in the URI of every jms inbound adapter
eg: "sjms2:some-topic?exceptionListener=#myExceptionListener"
2. Extend SjmsComponent2 to set the ExceptionListener on the Sjms2Component
{code:java}
ExceptionListener myExceptionListener = ex -> handleException(ex);
Sjms2Component jmsComponent = new Sjms2Component() {
protected SjmsEndpoint createSjmsEndpoint(String uri, String remaining) {
SjmsEndpoint endpoint = new Sjms2Endpoint(uri, this, remaining);
endpoint.setExceptionListener(exceptionListener);
return endpoint;
}
}{code}
I'd like to request that setExceptionListener(...) be added to SjmsComponent
(which will be inherited by Sjms2Component)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (CAMEL-18187) slack: inconsistent message payload when batch ends
[
https://issues.apache.org/jira/browse/CAMEL-18187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18187:
Fix Version/s: 3.18.0
> slack: inconsistent message payload when batch ends
> ---
>
> Key: CAMEL-18187
> URL: https://issues.apache.org/jira/browse/CAMEL-18187
> Project: Camel
> Issue Type: Bug
> Components: camel-slack
>Reporter: Luca Burgazzoli
>Priority: Major
> Fix For: 3.18.0
>
>
> When polling multiple events from slack, there is an inconsistent of the
> payload generated for the exchange that complete the batch:
> - This is an exchange part of the batch (CamelBatchComplete=false) and as it
> can be observed, the bodyType is com.slack.api.model.Message
> {code}
> 10:47:28.470 INFO [raw] (Camel (camel-1) thread #1 - slack://demo) Exchange[
> Id: B2F6BECBBE1B6C2-0001
> ExchangePattern: InOnly
> Properties:
> {camel.route.route1.B2F6BECBBE1B6C2-0001=io.smallrye.metrics.app.TimerImpl$Context@1bcda3c3,
> CamelBatchComplete=false, CamelBatchIndex=0, CamelBatchSize=2,
> CamelToEndpoint=log://raw?multiline=true=true,
> eventTimer:camel.exchange=io.smallrye.metrics.app.TimerImpl@7d791b4c,
> eventTimerContext:camel.exchange=io.smallrye.metrics.app.TimerImpl$Context@53f8d078}
> Headers: {}
> BodyType: com.slack.api.model.Message
> Body: Message(...)
> ]
> {code}
> - This is the exchange that closes the batch (CamelBatchComplete=true) and as
> it can be observed, the bodyType is byte[]:
> {code}
> 10:47:28.477 INFO [raw] (Camel (camel-1) thread #1 - slack://demo) Exchange[
> Id: B2F6BECBBE1B6C2-0001
> ExchangePattern: InOnly
> Properties:
> {camel.route.route1.B2F6BECBBE1B6C2-0001=io.smallrye.metrics.app.TimerImpl$Context@328e8fdf,
> CamelBatchComplete=true, CamelBatchIndex=1, CamelBatchSize=2,
> CamelToEndpoint=log://raw?multiline=true=true,
> eventTimer:camel.exchange=io.smallrye.metrics.app.TimerImpl@7d791b4c,
> eventTimerContext:camel.exchange=io.smallrye.metrics.app.TimerImpl$Context@53f8d078}
> Headers: {Content-Type=application/json,
> org.apache.kafka.clients.producer.RecordMetadata=[]}
> BodyType: byte[]
> Body: {"type":"message","subtype":"bot_message", ... }
> ]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Assigned] (CAMEL-18187) slack: inconsistent message payload when batch ends
[
https://issues.apache.org/jira/browse/CAMEL-18187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-18187:
---
Assignee: Claus Ibsen
> slack: inconsistent message payload when batch ends
> ---
>
> Key: CAMEL-18187
> URL: https://issues.apache.org/jira/browse/CAMEL-18187
> Project: Camel
> Issue Type: Bug
> Components: camel-slack
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.18.0
>
>
> When polling multiple events from slack, there is an inconsistent of the
> payload generated for the exchange that complete the batch:
> - This is an exchange part of the batch (CamelBatchComplete=false) and as it
> can be observed, the bodyType is com.slack.api.model.Message
> {code}
> 10:47:28.470 INFO [raw] (Camel (camel-1) thread #1 - slack://demo) Exchange[
> Id: B2F6BECBBE1B6C2-0001
> ExchangePattern: InOnly
> Properties:
> {camel.route.route1.B2F6BECBBE1B6C2-0001=io.smallrye.metrics.app.TimerImpl$Context@1bcda3c3,
> CamelBatchComplete=false, CamelBatchIndex=0, CamelBatchSize=2,
> CamelToEndpoint=log://raw?multiline=true=true,
> eventTimer:camel.exchange=io.smallrye.metrics.app.TimerImpl@7d791b4c,
> eventTimerContext:camel.exchange=io.smallrye.metrics.app.TimerImpl$Context@53f8d078}
> Headers: {}
> BodyType: com.slack.api.model.Message
> Body: Message(...)
> ]
> {code}
> - This is the exchange that closes the batch (CamelBatchComplete=true) and as
> it can be observed, the bodyType is byte[]:
> {code}
> 10:47:28.477 INFO [raw] (Camel (camel-1) thread #1 - slack://demo) Exchange[
> Id: B2F6BECBBE1B6C2-0001
> ExchangePattern: InOnly
> Properties:
> {camel.route.route1.B2F6BECBBE1B6C2-0001=io.smallrye.metrics.app.TimerImpl$Context@328e8fdf,
> CamelBatchComplete=true, CamelBatchIndex=1, CamelBatchSize=2,
> CamelToEndpoint=log://raw?multiline=true=true,
> eventTimer:camel.exchange=io.smallrye.metrics.app.TimerImpl@7d791b4c,
> eventTimerContext:camel.exchange=io.smallrye.metrics.app.TimerImpl$Context@53f8d078}
> Headers: {Content-Type=application/json,
> org.apache.kafka.clients.producer.RecordMetadata=[]}
> BodyType: byte[]
> Body: {"type":"message","subtype":"bot_message", ... }
> ]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (CAMEL-18194) camel-jbang - Consolidate download helper to be setup once
[ https://issues.apache.org/jira/browse/CAMEL-18194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18194: Description: TODO: add interface for downloader *DONE* TODO: setup instance once and store in camel context for reuse *DONE* TODO: capture metrics for downloader and add dev-console to expose data was: TODO: add interface for downloader TODO: setup instance once and store in camel context for reuse TODO: capture metrics for downloader and add dev-console to expose data > camel-jbang - Consolidate download helper to be setup once > -- > > Key: CAMEL-18194 > URL: https://issues.apache.org/jira/browse/CAMEL-18194 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.18.0 > > > TODO: add interface for downloader *DONE* > TODO: setup instance once and store in camel context for reuse *DONE* > TODO: capture metrics for downloader and add dev-console to expose data -- This message was sent by Atlassian Jira (v8.20.7#820007)
