[jira] [Commented] (CAMEL-18275) onCompletion tasks don't get executed in a pipeline with several SEDA queues
[
https://issues.apache.org/jira/browse/CAMEL-18275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17651800#comment-17651800
]
Babak Vahdat commented on CAMEL-18275:
--
Hi [~klease78]
As I was back-porting CAMEL-18835 I noticed that this fix in not back-ported
into the {{camel-3.18.x}} or {{camel-3.14.x}} LTS branches, but maybe that was
on purpose?
> onCompletion tasks don't get executed in a pipeline with several SEDA queues
>
>
> Key: CAMEL-18275
> URL: https://issues.apache.org/jira/browse/CAMEL-18275
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.18.0
>Reporter: Eduard Gomoliako
>Assignee: Karen Lease
>Priority: Major
> Fix For: 3.19.0
>
>
> I stumbled upon a problem with not working {{onCompletion}} between the
> routes that pass a message over SEDA queues.
> The route configuration is similar to this simplified version:
>
> {code:java}
> from("direct:a")
> .onCompletion().log("a - done").end()
> .to("seda:b");
> from("seda:b")
> .onCompletion().log("b - done").end()
> .to("seda:c");
> from("seda:c")
> .onCompletion().log("c - done").end()
> .to("seda:d");
> from("seda:d")
> .onCompletion().log("d - done").end()
> .to("mock:end"); {code}
>
> With this configuration, I get only {{"d - done"}} logging.
> I debugged the execution and noticed that the {{onCompletion}} handler from
> "a", "b", and "c" don't get executed because they are route-scoped and get
> attempted to be executed in the scope of the next route.
> This happens because they get handed over from the initial exchange to an
> exchange prepared for the next route. It happens in the
> {{SedaProducer::addToQueue}} method with {{{}copy{}}}parameter defined as
> {{{}true{}}}, which makes the {{::prepareCopy}} method being called, which in
> its turn calls {{ExchangeHelper.createCorrelatedCopy}} with {{handover}}
> defined as {{{}true{}}}.
> It seems to me like a bug, because looking at the routes configuration I'd
> expect different behavior: all the {{onCompletion}} tasks get executed
> reporting on routes finalization. Though maybe I'm missing something here,
> and if this is the case then I would appreciate you guys helping me to find
> out the missing details.
> Here is a [unit test reproducing the
> problem|https://gist.github.com/Gems/7555776feae619ac71ed8d9dd9d4d33e].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18835) camel-core-processor: OnCompletionProcessor#onFailure callback fires more than once
[ https://issues.apache.org/jira/browse/CAMEL-18835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat resolved CAMEL-18835. -- Resolution: Fixed > camel-core-processor: OnCompletionProcessor#onFailure callback fires more > than once > --- > > Key: CAMEL-18835 > URL: https://issues.apache.org/jira/browse/CAMEL-18835 > Project: Camel > Issue Type: Bug > Components: camel-core-processor >Affects Versions: 3.20.0 >Reporter: Babak Vahdat >Assignee: Babak Vahdat >Priority: Minor > Fix For: 3.14.8, 3.18.5, 3.20.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18835) camel-core-processor: OnCompletionProcessor#onFailure callback fires more than once
[ https://issues.apache.org/jira/browse/CAMEL-18835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat updated CAMEL-18835: - Fix Version/s: 3.14.8 > camel-core-processor: OnCompletionProcessor#onFailure callback fires more > than once > --- > > Key: CAMEL-18835 > URL: https://issues.apache.org/jira/browse/CAMEL-18835 > Project: Camel > Issue Type: Bug > Components: camel-core-processor >Affects Versions: 3.20.0 >Reporter: Babak Vahdat >Assignee: Babak Vahdat >Priority: Minor > Fix For: 3.14.8, 3.18.5, 3.20.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18835) camel-core-processor: OnCompletionProcessor#onFailure callback fires more than once
[ https://issues.apache.org/jira/browse/CAMEL-18835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat updated CAMEL-18835: - Summary: camel-core-processor: OnCompletionProcessor#onFailure callback fires more than once (was: camel-core: OnCompletionProcessor#onFailure callback fires more than once) > camel-core-processor: OnCompletionProcessor#onFailure callback fires more > than once > --- > > Key: CAMEL-18835 > URL: https://issues.apache.org/jira/browse/CAMEL-18835 > Project: Camel > Issue Type: Bug > Components: camel-core-processor >Affects Versions: 3.20.0 >Reporter: Babak Vahdat >Assignee: Babak Vahdat >Priority: Minor > Fix For: 3.18.5, 3.20.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18835) camel-core: OnCompletionProcessor#onFailure callback fires more than once
[ https://issues.apache.org/jira/browse/CAMEL-18835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat updated CAMEL-18835: - Summary: camel-core: OnCompletionProcessor#onFailure callback fires more than once (was: OnCompletionProcessor#onFailure callback fires more than once) > camel-core: OnCompletionProcessor#onFailure callback fires more than once > - > > Key: CAMEL-18835 > URL: https://issues.apache.org/jira/browse/CAMEL-18835 > Project: Camel > Issue Type: Bug > Components: camel-core-processor >Affects Versions: 3.20.0 >Reporter: Babak Vahdat >Assignee: Babak Vahdat >Priority: Minor > Fix For: 3.18.5, 3.20.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18835) OnCompletionProcessor#onFailure callback fires more than once
Babak Vahdat created CAMEL-18835: Summary: OnCompletionProcessor#onFailure callback fires more than once Key: CAMEL-18835 URL: https://issues.apache.org/jira/browse/CAMEL-18835 Project: Camel Issue Type: Bug Components: camel-core-processor Affects Versions: 3.20.0 Reporter: Babak Vahdat Assignee: Babak Vahdat Fix For: 3.18.5, 3.20.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18661) Camel OpenTelemtery instrumentation does not make spans current
[
https://issues.apache.org/jira/browse/CAMEL-18661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17649455#comment-17649455
]
Babak Vahdat commented on CAMEL-18661:
--
Hi [~Molkova]
As per conversation
[here|https://github.com/apache/camel/pull/8911#issuecomment-1355233167] just
to let you know that the flaky test has popped up on Jenkins build as well:
https://ci-builds.apache.org/job/Camel/job/Camel%20JDK11%20Build%20(S390x)/job/main/409/testReport/junit/org.apache.camel.opentelemetry/CurrentSpanTest/testContextDoesNotLeak/
{code}
org.apache.camel.CamelExecutionException: Exception occurred during execution
on the exchange: Exchange[1E6AD74DFFAFE6E-000A]
at
org.apache.camel.CamelExecutionException.wrapCamelExecutionException(CamelExecutionException.java:45)
at
org.apache.camel.support.AbstractExchange.setException(AbstractExchange.java:597)
at
org.apache.camel.support.DefaultExchange.setException(DefaultExchange.java:27)
at
org.apache.camel.processor.MulticastProcessor$MulticastTask.aggregate(MulticastProcessor.java:445)
at
org.apache.camel.processor.MulticastProcessor$MulticastReactiveTask.lambda$run$0(MulticastProcessor.java:570)
at org.apache.camel.AsyncCallback.run(AsyncCallback.java:44)
at
org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:181)
at
org.apache.camel.impl.engine.DefaultReactiveExecutor.schedule(DefaultReactiveExecutor.java:54)
at
org.apache.camel.processor.MulticastProcessor.lambda$schedule$1(MulticastProcessor.java:336)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: org.opentest4j.AssertionFailedError: expected: but was:
at
org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
at
org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
at org.junit.jupiter.api.AssertFalse.failNotFalse(AssertFalse.java:63)
at org.junit.jupiter.api.AssertFalse.assertFalse(AssertFalse.java:36)
at org.junit.jupiter.api.AssertFalse.assertFalse(AssertFalse.java:31)
at org.junit.jupiter.api.Assertions.assertFalse(Assertions.java:228)
at
org.apache.camel.opentelemetry.CurrentSpanTest$1.lambda$configure$0(CurrentSpanTest.java:221)
at
org.apache.camel.AggregationStrategy.aggregate(AggregationStrategy.java:86)
at
org.apache.camel.processor.MulticastProcessor.doAggregateInternal(MulticastProcessor.java:882)
at
org.apache.camel.processor.MulticastProcessor.doAggregateSync(MulticastProcessor.java:863)
at
org.apache.camel.processor.MulticastProcessor.doAggregate(MulticastProcessor.java:848)
at
org.apache.camel.processor.MulticastProcessor$MulticastTask.aggregate(MulticastProcessor.java:439)
... 10 more
{code}
> Camel OpenTelemtery instrumentation does not make spans current
>
>
> Key: CAMEL-18661
> URL: https://issues.apache.org/jira/browse/CAMEL-18661
> Project: Camel
> Issue Type: Bug
> Components: camel-opentelemetry
>Affects Versions: 3.19.0
> Environment: any, functional issue
>Reporter: Liudmila
>Priority: Minor
> Fix For: 3.20.0
>
> Attachments: camel_and_service_bus.png
>
>
> I have the following application:
>
> {code:java}
> @Component
> public class SourceRoute extends EndpointRouteBuilder {
> private static final String cs = "...";
> @Override
> public void configure() {
>from(timer("tick").period(1000).repeatCount(1))
> .log("Timer triggered")
> .setBody(simple("hello"))
> .to(azureServicebus("testme").
> serviceBusType("topic").
> connectionString(cs));
> }
> } {code}
>
> And I run it with [OpenTelemtery Java
> agent|https://github.com/open-telemetry/opentelemetry-java-instrumentation/].
> Camel creates "tick" and "testme" spans.
> ServiceBus SDK is instrumented too and it creates it's own spans.
> h2. Actual behavior:
> Spans created by ServiceBus SDK are unrelated to Camel spans. I.e. ServiceBus
> spans and Camel spans are in different traces (check out the attached
> screenshot).
> h2. Expected behavior:
> Camel "testme" span is a parent of ServiceBus spans:
> * tick
> ** testme
> *** ServiceBus.message
>
[jira] [Commented] (CAMEL-18661) Camel OpenTelemtery instrumentation does not make spans current
[
https://issues.apache.org/jira/browse/CAMEL-18661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17648599#comment-17648599
]
Babak Vahdat commented on CAMEL-18661:
--
Please review: https://github.com/apache/camel/pull/8911
> Camel OpenTelemtery instrumentation does not make spans current
>
>
> Key: CAMEL-18661
> URL: https://issues.apache.org/jira/browse/CAMEL-18661
> Project: Camel
> Issue Type: Bug
> Components: camel-opentelemetry
>Affects Versions: 3.19.0
> Environment: any, functional issue
>Reporter: Liudmila
>Priority: Minor
> Fix For: 3.20.0
>
> Attachments: camel_and_service_bus.png
>
>
> I have the following application:
>
> {code:java}
> @Component
> public class SourceRoute extends EndpointRouteBuilder {
> private static final String cs = "...";
> @Override
> public void configure() {
>from(timer("tick").period(1000).repeatCount(1))
> .log("Timer triggered")
> .setBody(simple("hello"))
> .to(azureServicebus("testme").
> serviceBusType("topic").
> connectionString(cs));
> }
> } {code}
>
> And I run it with [OpenTelemtery Java
> agent|https://github.com/open-telemetry/opentelemetry-java-instrumentation/].
> Camel creates "tick" and "testme" spans.
> ServiceBus SDK is instrumented too and it creates it's own spans.
> h2. Actual behavior:
> Spans created by ServiceBus SDK are unrelated to Camel spans. I.e. ServiceBus
> spans and Camel spans are in different traces (check out the attached
> screenshot).
> h2. Expected behavior:
> Camel "testme" span is a parent of ServiceBus spans:
> * tick
> ** testme
> *** ServiceBus.message
> *** ServiceBus.send
> h2. Investigation
> If I look into the OTel instrumentation code (and debug my application). I
> can see that OTel span starts here
> https://github.com/apache/camel/blob/1175c2666821457dcb6cf0921f4076508459341a/components/camel-opentelemetry/src/main/java/org/apache/camel/opentelemetry/OpenTelemetryTracer.java#L92
> and then is 'activated' here
> https://github.com/apache/camel/blob/main/components/camel-tracing/src/main/java/org/apache/camel/tracing/Tracer.java#L248
> But the activation code only puts trace_id and span_id on MDC.
> The proposal for Camel is to make OpenTelemtery span active (using
> Span.makeCurrent()).
> This is the only way underlying traces can be correlated to Camel spans.
> {code:java}
> try (Scope s = span.makeCurrent()) {
>// wrap processing, but always clean up the scope to avoid leaks
> } {code}
> OTel instrumentation will take care of propagating this context anywhere else.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18661) Camel OpenTelemtery instrumentation does not make spans current
[
https://issues.apache.org/jira/browse/CAMEL-18661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17648427#comment-17648427
]
Babak Vahdat commented on CAMEL-18661:
--
Should we look into backporting this for the upcoming {{3.18.5}} LTS release?
> Camel OpenTelemtery instrumentation does not make spans current
>
>
> Key: CAMEL-18661
> URL: https://issues.apache.org/jira/browse/CAMEL-18661
> Project: Camel
> Issue Type: Bug
> Components: camel-opentelemetry
>Affects Versions: 3.19.0
> Environment: any, functional issue
>Reporter: Liudmila
>Priority: Minor
> Fix For: 3.20.0
>
> Attachments: camel_and_service_bus.png
>
>
> I have the following application:
>
> {code:java}
> @Component
> public class SourceRoute extends EndpointRouteBuilder {
> private static final String cs = "...";
> @Override
> public void configure() {
>from(timer("tick").period(1000).repeatCount(1))
> .log("Timer triggered")
> .setBody(simple("hello"))
> .to(azureServicebus("testme").
> serviceBusType("topic").
> connectionString(cs));
> }
> } {code}
>
> And I run it with [OpenTelemtery Java
> agent|https://github.com/open-telemetry/opentelemetry-java-instrumentation/].
> Camel creates "tick" and "testme" spans.
> ServiceBus SDK is instrumented too and it creates it's own spans.
> h2. Actual behavior:
> Spans created by ServiceBus SDK are unrelated to Camel spans. I.e. ServiceBus
> spans and Camel spans are in different traces (check out the attached
> screenshot).
> h2. Expected behavior:
> Camel "testme" span is a parent of ServiceBus spans:
> * tick
> ** testme
> *** ServiceBus.message
> *** ServiceBus.send
> h2. Investigation
> If I look into the OTel instrumentation code (and debug my application). I
> can see that OTel span starts here
> https://github.com/apache/camel/blob/1175c2666821457dcb6cf0921f4076508459341a/components/camel-opentelemetry/src/main/java/org/apache/camel/opentelemetry/OpenTelemetryTracer.java#L92
> and then is 'activated' here
> https://github.com/apache/camel/blob/main/components/camel-tracing/src/main/java/org/apache/camel/tracing/Tracer.java#L248
> But the activation code only puts trace_id and span_id on MDC.
> The proposal for Camel is to make OpenTelemtery span active (using
> Span.makeCurrent()).
> This is the only way underlying traces can be correlated to Camel spans.
> {code:java}
> try (Scope s = span.makeCurrent()) {
>// wrap processing, but always clean up the scope to avoid leaks
> } {code}
> OTel instrumentation will take care of propagating this context anywhere else.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18809) camel-core-model: RouteDefinitionHelper should resolve the intercepted from URI which is configured with property placeholder
[ https://issues.apache.org/jira/browse/CAMEL-18809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat resolved CAMEL-18809. -- Resolution: Fixed > camel-core-model: RouteDefinitionHelper should resolve the intercepted from > URI which is configured with property placeholder > - > > Key: CAMEL-18809 > URL: https://issues.apache.org/jira/browse/CAMEL-18809 > Project: Camel > Issue Type: Bug > Components: camel-core-model >Affects Versions: 3.18.4 >Reporter: Babak Vahdat >Assignee: Babak Vahdat >Priority: Minor > Fix For: 3.18.5, 3.20.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18809) camel-core-model: RouteDefinitionHelper should resolve the intercepted from URI which is configured with property placeholder
[ https://issues.apache.org/jira/browse/CAMEL-18809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat updated CAMEL-18809: - Issue Type: Bug (was: Task) > camel-core-model: RouteDefinitionHelper should resolve the intercepted from > URI which is configured with property placeholder > - > > Key: CAMEL-18809 > URL: https://issues.apache.org/jira/browse/CAMEL-18809 > Project: Camel > Issue Type: Bug > Components: camel-core-model >Affects Versions: 3.18.4 >Reporter: Babak Vahdat >Assignee: Babak Vahdat >Priority: Minor > Fix For: 3.18.5 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18809) camel-core-model: RouteDefinitionHelper should resolve the intercepted from URI which is configured with property placeholder
Babak Vahdat created CAMEL-18809: Summary: camel-core-model: RouteDefinitionHelper should resolve the intercepted from URI which is configured with property placeholder Key: CAMEL-18809 URL: https://issues.apache.org/jira/browse/CAMEL-18809 Project: Camel Issue Type: Task Components: camel-core-model Affects Versions: 3.18.4 Reporter: Babak Vahdat Assignee: Babak Vahdat Fix For: 3.18.5 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (CAMEL-18541) Camel Azure ServiceBusProducer ignore CamelAzureServiceBusApplicationProperties
[ https://issues.apache.org/jira/browse/CAMEL-18541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat closed CAMEL-18541. Assignee: Babak Vahdat Resolution: Won't Fix Closing as the next LTS release is coming out [soon|https://lists.apache.org/thread/83yz2wq60dgovb72d5jwvq0z47s794kf] which would include the fix for this. > Camel Azure ServiceBusProducer ignore > CamelAzureServiceBusApplicationProperties > --- > > Key: CAMEL-18541 > URL: https://issues.apache.org/jira/browse/CAMEL-18541 > Project: Camel > Issue Type: New Feature > Components: camel-azure >Reporter: Samo Abuhaseera >Assignee: Babak Vahdat >Priority: Major > Fix For: 3.x > > > This is related to camel-azure-servicebus component. > The Azure serviceBus Java SDK has a feature allows sender to send > ApplicationProperties (Map metadata associated with the ServiceBusReceivedMessage, during Service Bus > operations. > This feature is not present in Camel ServiceBusProducer. It sends only the > camel Message body to service bus. There is not a feature to pass meta data > such as ApplicationProperties. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18541) Camel Azure ServiceBusProducer ignore CamelAzureServiceBusApplicationProperties
[
https://issues.apache.org/jira/browse/CAMEL-18541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609111#comment-17609111
]
Babak Vahdat commented on CAMEL-18541:
--
{quote}However I wonder what happens if you do a
from azure a
to log
to azure b
then that CamelAzureServiceBusApplicationProperties would that propagate those
headers from a to b, and if so is this correct?
{quote}
Good point, I think that is what would happen which is the _default_ behaviour
in Camel to propagate headers from one node to the next. E.g. if this was JMS
(instead of EventHubs) then Camel would do the same to copy the corresponding
headers of that consumed JMS message to the target, right? And if this is not
the wished behaviour then {{removeHeader}} or {{removeHeaders}} EIP needs to be
used for that concrete given use-case.
This also seems to be a similar behaviour when they deserialize the underlying
consumed Qpid Proton message:
https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/core/azure-core-amqp/src/main/java/com/azure/core/amqp/implementation/MessageUtils.java#L195
> Camel Azure ServiceBusProducer ignore
> CamelAzureServiceBusApplicationProperties
> ---
>
> Key: CAMEL-18541
> URL: https://issues.apache.org/jira/browse/CAMEL-18541
> Project: Camel
> Issue Type: New Feature
> Components: camel-azure
>Reporter: Samo Abuhaseera
>Priority: Major
> Fix For: 3.x
>
>
> This is related to camel-azure-servicebus component.
> The Azure serviceBus Java SDK has a feature allows sender to send
> ApplicationProperties (Map metadata associated with the ServiceBusReceivedMessage, during Service Bus
> operations.
> This feature is not present in Camel ServiceBusProducer. It sends only the
> camel Message body to service bus. There is not a feature to pass meta data
> such as ApplicationProperties.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18541) Camel Azure ServiceBusProducer ignore CamelAzureServiceBusApplicationProperties
[
https://issues.apache.org/jira/browse/CAMEL-18541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608692#comment-17608692
]
Babak Vahdat commented on CAMEL-18541:
--
See the {{Fix Version/s}} label of CAMEL-18459 which points to the non-LTS
version {{3.19.0}}.
So maybe backporting of the JIRA above to the {{3.18.x}} LTS branch would be
what you are looking for?
[~davsclaus] can that be done? If so, I could look into backporting it.
> Camel Azure ServiceBusProducer ignore
> CamelAzureServiceBusApplicationProperties
> ---
>
> Key: CAMEL-18541
> URL: https://issues.apache.org/jira/browse/CAMEL-18541
> Project: Camel
> Issue Type: New Feature
> Components: camel-azure
>Reporter: Samo Abuhaseera
>Priority: Major
> Fix For: 3.x
>
>
> This is related to camel-azure-servicebus component.
> The Azure serviceBus Java SDK has a feature allows sender to send
> ApplicationProperties (Map metadata associated with the ServiceBusReceivedMessage, during Service Bus
> operations.
> This feature is not present in Camel ServiceBusProducer. It sends only the
> camel Message body to service bus. There is not a feature to pass meta data
> such as ApplicationProperties.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18541) Camel Azure ServiceBusProducer ignore CamelAzureServiceBusApplicationProperties
[
https://issues.apache.org/jira/browse/CAMEL-18541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608669#comment-17608669
]
Babak Vahdat edited comment on CAMEL-18541 at 9/23/22 10:03 AM:
{quote}the producer reads the camel exchange body only and it ignores camel
headers. Ideally the camel exchange header
CamelAzureServiceBusApplicationProperties should be mapped to
serviceBusMessage.applicationProperties
{quote}
See
[here|https://github.com/apache/camel/blob/main/components/camel-azure/camel-azure-servicebus/src/main/java/org/apache/camel/component/azure/servicebus/ServiceBusProducer.java#L146-L147]
for what is out there on the main branch.
was (Author: bvahdat):
{quote}he producer reads the camel exchange body only and it ignores camel
headers. Ideally the camel exchange header
CamelAzureServiceBusApplicationProperties should be mapped to
serviceBusMessage.applicationProperties
{quote}
See
[here|https://github.com/apache/camel/blob/main/components/camel-azure/camel-azure-servicebus/src/main/java/org/apache/camel/component/azure/servicebus/ServiceBusProducer.java#L146-L147]
for what is out there on the main branch.
> Camel Azure ServiceBusProducer ignore
> CamelAzureServiceBusApplicationProperties
> ---
>
> Key: CAMEL-18541
> URL: https://issues.apache.org/jira/browse/CAMEL-18541
> Project: Camel
> Issue Type: New Feature
> Components: camel-azure
>Reporter: Samo Abuhaseera
>Priority: Major
> Fix For: 3.x
>
>
> This is related to camel-azure-servicebus component.
> The Azure serviceBus Java SDK has a feature allows sender to send
> ApplicationProperties (Map metadata associated with the ServiceBusReceivedMessage, during Service Bus
> operations.
> This feature is not present in Camel ServiceBusProducer. It sends only the
> camel Message body to service bus. There is not a feature to pass meta data
> such as ApplicationProperties.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18541) Camel Azure ServiceBusProducer ignore CamelAzureServiceBusApplicationProperties
[
https://issues.apache.org/jira/browse/CAMEL-18541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608669#comment-17608669
]
Babak Vahdat edited comment on CAMEL-18541 at 9/23/22 10:03 AM:
{quote}he producer reads the camel exchange body only and it ignores camel
headers. Ideally the camel exchange header
CamelAzureServiceBusApplicationProperties should be mapped to
serviceBusMessage.applicationProperties
{quote}
See
[here|https://github.com/apache/camel/blob/main/components/camel-azure/camel-azure-servicebus/src/main/java/org/apache/camel/component/azure/servicebus/ServiceBusProducer.java#L146-L147]
for what is out there on the main branch.
was (Author: bvahdat):
{quote}
he producer reads the camel exchange body only and it ignores camel headers.
Ideally the camel exchange header CamelAzureServiceBusApplicationProperties
should be mapped to serviceBusMessage.applicationProperties
{quote}
See
[here|https://github.com/apache/camel/blob/main/components/camel-azure/camel-azure-servicebus/src/main/java/org/apache/camel/component/azure/servicebus/ServiceBusProducer.java#L146-L147]
for what there is out there on the main branch.
> Camel Azure ServiceBusProducer ignore
> CamelAzureServiceBusApplicationProperties
> ---
>
> Key: CAMEL-18541
> URL: https://issues.apache.org/jira/browse/CAMEL-18541
> Project: Camel
> Issue Type: New Feature
> Components: camel-azure
>Reporter: Samo Abuhaseera
>Priority: Major
> Fix For: 3.x
>
>
> This is related to camel-azure-servicebus component.
> The Azure serviceBus Java SDK has a feature allows sender to send
> ApplicationProperties (Map metadata associated with the ServiceBusReceivedMessage, during Service Bus
> operations.
> This feature is not present in Camel ServiceBusProducer. It sends only the
> camel Message body to service bus. There is not a feature to pass meta data
> such as ApplicationProperties.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18541) Camel Azure ServiceBusProducer ignore CamelAzureServiceBusApplicationProperties
[
https://issues.apache.org/jira/browse/CAMEL-18541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608669#comment-17608669
]
Babak Vahdat commented on CAMEL-18541:
--
{quote}
he producer reads the camel exchange body only and it ignores camel headers.
Ideally the camel exchange header CamelAzureServiceBusApplicationProperties
should be mapped to serviceBusMessage.applicationProperties
{quote}
See
[here|https://github.com/apache/camel/blob/main/components/camel-azure/camel-azure-servicebus/src/main/java/org/apache/camel/component/azure/servicebus/ServiceBusProducer.java#L146-L147]
for what there is out there on the main branch.
> Camel Azure ServiceBusProducer ignore
> CamelAzureServiceBusApplicationProperties
> ---
>
> Key: CAMEL-18541
> URL: https://issues.apache.org/jira/browse/CAMEL-18541
> Project: Camel
> Issue Type: New Feature
> Components: camel-azure
>Reporter: Samo Abuhaseera
>Priority: Major
> Fix For: 3.x
>
>
> This is related to camel-azure-servicebus component.
> The Azure serviceBus Java SDK has a feature allows sender to send
> ApplicationProperties (Map metadata associated with the ServiceBusReceivedMessage, during Service Bus
> operations.
> This feature is not present in Camel ServiceBusProducer. It sends only the
> camel Message body to service bus. There is not a feature to pass meta data
> such as ApplicationProperties.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18541) Camel Azure ServiceBusProducer ignore CamelAzureServiceBusApplicationProperties
[ https://issues.apache.org/jira/browse/CAMEL-18541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608630#comment-17608630 ] Babak Vahdat commented on CAMEL-18541: -- Maybe CAMEL-18459 is what you are looking for? See also https://camel.apache.org/components/next/azure-servicebus-component.html#_endpoint_header_CamelAzureServiceBusApplicationProperties > Camel Azure ServiceBusProducer ignore > CamelAzureServiceBusApplicationProperties > --- > > Key: CAMEL-18541 > URL: https://issues.apache.org/jira/browse/CAMEL-18541 > Project: Camel > Issue Type: New Feature > Components: camel-azure >Reporter: Samo Abuhaseera >Priority: Major > Fix For: 3.x > > > This is related to camel-azure-servicebus component. > The Azure serviceBus Java SDK has a feature allows sender to send > ApplicationProperties (Map metadata associated with the ServiceBusReceivedMessage, during Service Bus > operations. > This feature is not present in Camel ServiceBusProducer. It sends only the > camel Message body to service bus. There is not a feature to pass meta data > such as ApplicationProperties. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18451) camel-azure-eventhubs: Add support for Azure-AD authentication
[ https://issues.apache.org/jira/browse/CAMEL-18451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat resolved CAMEL-18451. -- Resolution: Fixed > camel-azure-eventhubs: Add support for Azure-AD authentication > -- > > Key: CAMEL-18451 > URL: https://issues.apache.org/jira/browse/CAMEL-18451 > Project: Camel > Issue Type: New Feature > Components: camel-azure-eventhubs >Affects Versions: 3.18.1 >Reporter: Babak Vahdat >Assignee: Babak Vahdat >Priority: Major > Fix For: 3.18.3, 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18451) camel-azure-eventhubs: Add support for Azure-AD authentication
[
https://issues.apache.org/jira/browse/CAMEL-18451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17602727#comment-17602727
]
Babak Vahdat edited comment on CAMEL-18451 at 9/10/22 4:17 PM:
---
{quote}Oh I was not aware. I wonder if you can do backport without the PR.
{quote}
Please review [https://github.com/apache/camel/pull/8348]
I skipped to backport all the commits on July 22th which were all part of that
improvement I mentioned above provided by Kévin Lacire.
[https://github.com/apache/camel/commits/main/components/camel-azure/camel-azure-eventhubs]
Additionally all the azure-XXX dependencies are aligned with {{azure-sdk-bom}}
version {{1.2.5}}
[https://mvnrepository.com/artifact/com.azure/azure-sdk-bom/1.2.5]
On the 3.18.x branch verified the successful execution of the integration tests
as well as the functionality of this new feature.
was (Author: bvahdat):
{quote}Oh I was not aware. I wonder if you can do backport without the PR.
{quote}
Please review [https://github.com/apache/camel/pull/8348]
I skipped to backport all the commits on July 22th which were all part of that
improvement I mentioned above provided by Kévin Lacire.
[https://github.com/apache/camel/commits/main/components/camel-azure/camel-azure-eventhubs]
Additionally all the azure-XXX dependencies are aligned with {{azure-sdk-bom}}
version {{1.2.5}}
[https://mvnrepository.com/artifact/com.azure/azure-sdk-bom/1.2.5]
> camel-azure-eventhubs: Add support for Azure-AD authentication
> --
>
> Key: CAMEL-18451
> URL: https://issues.apache.org/jira/browse/CAMEL-18451
> Project: Camel
> Issue Type: New Feature
> Components: camel-azure-eventhubs
>Affects Versions: 3.18.1
>Reporter: Babak Vahdat
>Assignee: Babak Vahdat
>Priority: Major
> Fix For: 3.18.3, 3.19.0
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18451) camel-azure-eventhubs: Add support for Azure-AD authentication
[ https://issues.apache.org/jira/browse/CAMEL-18451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat updated CAMEL-18451: - Fix Version/s: 3.18.3 > camel-azure-eventhubs: Add support for Azure-AD authentication > -- > > Key: CAMEL-18451 > URL: https://issues.apache.org/jira/browse/CAMEL-18451 > Project: Camel > Issue Type: New Feature > Components: camel-azure-eventhubs >Affects Versions: 3.18.1 >Reporter: Babak Vahdat >Assignee: Babak Vahdat >Priority: Major > Fix For: 3.18.3, 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18451) camel-azure-eventhubs: Add support for Azure-AD authentication
[
https://issues.apache.org/jira/browse/CAMEL-18451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17602727#comment-17602727
]
Babak Vahdat commented on CAMEL-18451:
--
{quote}Oh I was not aware. I wonder if you can do backport without the PR.
{quote}
Please review [https://github.com/apache/camel/pull/8348]
I skipped to backport all the commits on July 22th which were all part of that
improvement I mentioned above provided by Kévin Lacire.
[https://github.com/apache/camel/commits/main/components/camel-azure/camel-azure-eventhubs]
Additionally all the azure-XXX dependencies are aligned with {{azure-sdk-bom}}
version {{1.2.5}}
[https://mvnrepository.com/artifact/com.azure/azure-sdk-bom/1.2.5]
> camel-azure-eventhubs: Add support for Azure-AD authentication
> --
>
> Key: CAMEL-18451
> URL: https://issues.apache.org/jira/browse/CAMEL-18451
> Project: Camel
> Issue Type: New Feature
> Components: camel-azure-eventhubs
>Affects Versions: 3.18.1
>Reporter: Babak Vahdat
>Assignee: Babak Vahdat
>Priority: Major
> Fix For: 3.19.0
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18451) camel-azure-eventhubs: Add support for Azure-AD authentication
[ https://issues.apache.org/jira/browse/CAMEL-18451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17602637#comment-17602637 ] Babak Vahdat commented on CAMEL-18451: -- I get couple of merge conflicts to backport because of the following improvement not available on the 3.18.x branch: [https://github.com/apache/camel/commit/abd1350f1da60d1fa02295f27b8828978a12e61d] I was not able to find the corresponding ticket for it. Should I backport this improvement as well? > camel-azure-eventhubs: Add support for Azure-AD authentication > -- > > Key: CAMEL-18451 > URL: https://issues.apache.org/jira/browse/CAMEL-18451 > Project: Camel > Issue Type: New Feature > Components: camel-azure-eventhubs >Affects Versions: 3.18.1 >Reporter: Babak Vahdat >Assignee: Babak Vahdat >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18451) camel-azure-eventhubs: Add support for Azure-AD authentication
[ https://issues.apache.org/jira/browse/CAMEL-18451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17602277#comment-17602277 ] Babak Vahdat commented on CAMEL-18451: -- [~davsclaus] can we backport this feature to the 3.18.x LTS branch? If so I would then provide the corresponding PR for that. > camel-azure-eventhubs: Add support for Azure-AD authentication > -- > > Key: CAMEL-18451 > URL: https://issues.apache.org/jira/browse/CAMEL-18451 > Project: Camel > Issue Type: Improvement > Components: camel-azure-eventhubs >Affects Versions: 3.18.1 >Reporter: Babak Vahdat >Assignee: Babak Vahdat >Priority: Minor > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18451) camel-azure-eventhubs: Add support for Azure-AD authentication
[ https://issues.apache.org/jira/browse/CAMEL-18451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600674#comment-17600674 ] Babak Vahdat commented on CAMEL-18451: -- _Off the topic_: Apparently I am already getting too old for all this. I had to edit the comment above X times to get it right... > camel-azure-eventhubs: Add support for Azure-AD authentication > -- > > Key: CAMEL-18451 > URL: https://issues.apache.org/jira/browse/CAMEL-18451 > Project: Camel > Issue Type: Improvement > Components: camel-azure-eventhubs >Affects Versions: 3.18.1 >Reporter: Babak Vahdat >Assignee: Babak Vahdat >Priority: Minor > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18451) camel-azure-eventhubs: Add support for Azure-AD authentication
[
https://issues.apache.org/jira/browse/CAMEL-18451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600636#comment-17600636
]
Babak Vahdat edited comment on CAMEL-18451 at 9/6/22 8:46 AM:
--
- {{{}camel-azure-servicebus{}}}: has already got that (explicit) support.
- {{{}camel-azure-cosmosdb{}}}: has got that (implicitly) through the
{{cosmosAsyncClient}} option which would do the job both for the consumer as
well as producer.
- {{camel-azure-storage-blob}} / {{camel-azure-storage-datalake}} /
{{{}camel-azure-storage-queue{}}}: the same as {{camel-azure-cosmosdb}} through
their {{serviceClient}} option.
That being said, I could be wrong and this needs to be verified first through
the corresponding integration tests which you would need your own azure
subscription for. And before integration testing, the corresponding resources
need to be configured to be accessible through Azure-AD authentication.
Something to be done through the Azure-Portal interface.
For 2) and 3) it would be nice to have this support explicitly (not implicitly)
then that required dependency (with the right version) for Azure-AD would be
already there for the users:
[https://github.com/apache/camel/blob/camel-3.18.2/components/camel-azure/camel-azure-servicebus/pom.xml#L56-L60]
And all they would need to provide is to bind a single {{TokenCredential}} into
the registry:
[https://camel.apache.org/components/3.18.x/azure-servicebus-component.html#_endpoint_query_option_tokenCredential]
was (Author: bvahdat):
- {{{}camel-azure-servicebus{}}}: has already got that (explicit) support.
- {{{}camel-azure-cosmosdb{}}}: has got that (implicitly) through the
{{cosmosAsyncClient}} option which would do the job both for the consumer as
well as producer.
-
{{camel-azure-storage-blob}} / {{camel-azure-storage-datalake}} /
{{{}camel-azure-storage-queue{}}}: the same as {{camel-azure-cosmosdb}} through
their {{serviceClient}} option.
That being said, I could be wrong and this needs to be verified first through
the corresponding integration tests which you would need your own azure
subscription for. And before integration testing, the corresponding resources
need to be configured to be accessible through Azure-AD authentication.
Something to be done through the Azure-Portal interface.
For 2) and 3) it would be nice to have this support explicitly (not implicitly)
then that required dependency (with the right version) for Azure-AD would be
already there for the users:
[https://github.com/apache/camel/blob/camel-3.18.2/components/camel-azure/camel-azure-servicebus/pom.xml#L56-L60]
And all they would need to provide is to bind a single {{TokenCredentail}} into
the registry:
[https://camel.apache.org/components/3.18.x/azure-servicebus-component.html#_endpoint_query_option_tokenCredential]
> camel-azure-eventhubs: Add support for Azure-AD authentication
> --
>
> Key: CAMEL-18451
> URL: https://issues.apache.org/jira/browse/CAMEL-18451
> Project: Camel
> Issue Type: Improvement
> Components: camel-azure-eventhubs
>Affects Versions: 3.18.1
>Reporter: Babak Vahdat
>Assignee: Babak Vahdat
>Priority: Minor
> Fix For: 3.19.0
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18451) camel-azure-eventhubs: Add support for Azure-AD authentication
[
https://issues.apache.org/jira/browse/CAMEL-18451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600636#comment-17600636
]
Babak Vahdat edited comment on CAMEL-18451 at 9/6/22 7:34 AM:
--
- {{{}camel-azure-servicebus{}}}: has already got that (explicit) support.
- {{{}camel-azure-cosmosdb{}}}: has got that (implicitly) through the
{{cosmosAsyncClient}} option which would do the job both for the consumer as
well as producer.
-
{{camel-azure-storage-blob}} / {{camel-azure-storage-datalake}} /
{{{}camel-azure-storage-queue{}}}: the same as {{camel-azure-cosmosdb}} through
their {{serviceClient}} option.
That being said, I could be wrong and this needs to be verified first through
the corresponding integration tests which you would need your own azure
subscription for. And before integration testing, the corresponding resources
need to be configured to be accessible through Azure-AD authentication.
Something to be done through the Azure-Portal interface.
For 2) and 3) it would be nice to have this support explicitly (not implicitly)
then that required dependency (with the right version) for Azure-AD would be
already there for the users:
[https://github.com/apache/camel/blob/camel-3.18.2/components/camel-azure/camel-azure-servicebus/pom.xml#L56-L60]
And all they would need to provide is to bind a single {{TokenCredentail}} into
the registry:
[https://camel.apache.org/components/3.18.x/azure-servicebus-component.html#_endpoint_query_option_tokenCredential]
was (Author: bvahdat):
- {{{}camel-azure-servicebus{}}}: has already got that (explicit) support.
- {{{}camel-azure-cosmosdb{}}}: has got that (implicitly) through the
{{cosmosAsyncClient}} option which would do the job both for the consumer as
well as producer.
- {{{}camel-{}}}{{{}azure-storage-blob{}}}/
{{{}camel-{}}}{{{}azure-storage-datalake{}}}/
{{{}camel-azure-{}}}{{{}storage-queue{}}}: the same as
{{{}camel-{}}}{{{}azure-cosmosdb {}}}through their {{serviceClient}} option.
That being said, I could be wrong and this needs to be verified first through
the corresponding integration tests which you would need your own azure
subscription for. And before integration testing, the corresponding resources
need to be configured to be accessible through Azure-AD authentication.
Something to be done through the Azure-Portal interface.
For 2) and 3) it would be nice to have this support explicitly (not implicitly)
then that required dependency (with the right version) for Azure-AD would be
already there for the users:
[https://github.com/apache/camel/blob/camel-3.18.2/components/camel-azure/camel-azure-servicebus/pom.xml#L56-L60]
And all they would need to provide is to bind a single {{TokenCredentail}} into
the registry:
[https://camel.apache.org/components/3.18.x/azure-servicebus-component.html#_endpoint_query_option_tokenCredential]
> camel-azure-eventhubs: Add support for Azure-AD authentication
> --
>
> Key: CAMEL-18451
> URL: https://issues.apache.org/jira/browse/CAMEL-18451
> Project: Camel
> Issue Type: Improvement
> Components: camel-azure-eventhubs
>Affects Versions: 3.18.1
>Reporter: Babak Vahdat
>Assignee: Babak Vahdat
>Priority: Minor
> Fix For: 3.19.0
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18451) camel-azure-eventhubs: Add support for Azure-AD authentication
[
https://issues.apache.org/jira/browse/CAMEL-18451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600636#comment-17600636
]
Babak Vahdat edited comment on CAMEL-18451 at 9/6/22 7:32 AM:
--
- {{{}camel-azure-servicebus{}}}: has already got that (explicit) support.
- {{{}camel-azure-cosmosdb{}}}: has got that (implicitly) through the
{{cosmosAsyncClient}} option which would do the job both for the consumer as
well as producer.
- {{{}camel-{}}}{{{}azure-storage-blob{}}}/
{{{}camel-{}}}{{{}azure-storage-datalake{}}}/
{{{}camel-azure-{}}}{{{}storage-queue{}}}: the same as
{{{}camel-{}}}{{{}azure-cosmosdb {}}}through their {{serviceClient}} option.
That being said, I could be wrong and this needs to be verified first through
the corresponding integration tests which you would need your own azure
subscription for. And before integration testing, the corresponding resources
need to be configured to be accessible through Azure-AD authentication.
Something to be done through the Azure-Portal interface.
For 2) and 3) it would be nice to have this support explicitly (not implicitly)
then that required dependency (with the right version) for Azure-AD would be
already there for the users:
[https://github.com/apache/camel/blob/camel-3.18.2/components/camel-azure/camel-azure-servicebus/pom.xml#L56-L60]
And all they would need to provide is to bind a single {{TokenCredentail}} into
the registry:
[https://camel.apache.org/components/3.18.x/azure-servicebus-component.html#_endpoint_query_option_tokenCredential]
was (Author: bvahdat):
- {{{}camel-azure-servicebus{}}}: has already got that (explicit) support.
- {{{}camel-azure-cosmosdb{}}}: has got that (implicitly) through the
{{cosmosAsyncClient}} option which would do the job both for the consumer as
well as producer.
- {{{}camel-{}}}{{{}azure-storage-blob{}}}/
{{{}camel-{}}}{{{}azure-storage-datalake{}}}/
{{{}camel-azure-{}}}{{{}storage-queue{}}}: the same as
{{{}camel-{}}}{{{}azure-cosmosdb {}}}through their {{serviceClient}} option.
That being said, I could be wrong and this needs to be verified first through
the corresponding integration tests which you would need your own azure
subscription for. And before integration testing, the corresponding resources
need to be configured to be accessible through Azure-AD authentication.
Something to be done through the Azure-Portal interface.
For 2) and 3) it would be nice to have this support explicitly (not implicitly)
then that required dependency (with the right version) for Azure-AD would be
already there for the users:
[https://github.com/apache/camel/blob/camel-3.18.2/components/camel-azure/camel-azure-servicebus/pom.xml#L56-L60]
And all they would need to provide is to bind a single {{TokenCredentail}} into
the registry:
[https://camel.apache.org/components/3.18.x/azure-servicebus-component.html#_endpoint_query_option_tokenCredential]
> camel-azure-eventhubs: Add support for Azure-AD authentication
> --
>
> Key: CAMEL-18451
> URL: https://issues.apache.org/jira/browse/CAMEL-18451
> Project: Camel
> Issue Type: Improvement
> Components: camel-azure-eventhubs
>Affects Versions: 3.18.1
>Reporter: Babak Vahdat
>Assignee: Babak Vahdat
>Priority: Minor
> Fix For: 3.19.0
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18451) camel-azure-eventhubs: Add support for Azure-AD authentication
[
https://issues.apache.org/jira/browse/CAMEL-18451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600636#comment-17600636
]
Babak Vahdat edited comment on CAMEL-18451 at 9/6/22 7:27 AM:
--
- {{{}camel-azure-servicebus{}}}: has already got that (explicit) support.
- {{{}camel-azure-cosmosdb{}}}: has got that (implicitly) through the
{{cosmosAsyncClient}} option which would do the job both for the consumer as
well as producer.
- {{{}camel-{}}}{{{}azure-storage-blob{}}}/
{{{}camel-{}}}{{{}azure-storage-datalake{}}}/
{{{}camel-azure-{}}}{{{}storage-queue{}}}: the same as
{{{}camel-{}}}{{{}azure-cosmosdb {}}}through their {{serviceClient}} option.
That being said, I could be wrong and this needs to be verified first through
the corresponding integration tests which you would need your own azure
subscription for. And before integration testing, the corresponding resources
need to be configured to be accessible through Azure-AD authentication.
Something to be done through the Azure-Portal interface.
For 2) and 3) it would be nice to have this support explicitly (not implicitly)
then that required dependency (with the right version) for Azure-AD would be
already there for the users:
[https://github.com/apache/camel/blob/camel-3.18.2/components/camel-azure/camel-azure-servicebus/pom.xml#L56-L60]
And all they would need to provide is to bind a single {{TokenCredentail}} into
the registry:
[https://camel.apache.org/components/3.18.x/azure-servicebus-component.html#_endpoint_query_option_tokenCredential]
was (Author: bvahdat):
- {{{}camel-azure-servicebus{}}}: has already got that (explicit) support.
- {{{}camel-azure-cosmosdb{}}}: has got that (implicitly) through the
{{cosmosAsyncClient}} option which would do the job both for the consumer as
well as producer.
- {{{}camel-{}}}{{{}azure-storage-blob{}}}/
{{{}camel-{}}}{{{}azure-storage-datalake{}}}/
{{{}camel-azure-{}}}{{{}storage-queue{}}}: the same as
{{{}camel-{}}}{{{}azure-cosmosdb {}}}through their {{serviceClient}} option.
That being said, I could be wrong and this needs to be verified first through
the corresponding integration tests which you would need your own azure
subscription for. And before integration testing, the corresponding resources
need to be configured to be accessible through Azure-AD authentication.
Something to be done through the Azure-Portal interface.
For 2) and 3) it would be nice to have this support explicitly (not implicitly)
then that required dependency (with the right version) for Azure-AD would be
already there for the users:
[https://github.com/apache/camel/blob/camel-3.18.2/components/camel-azure/camel-azure-servicebus/pom.xml#L56-L60]
And all they would need to provide is to bind a single {{TokenCredentail}} into
the registry:
[https://camel.apache.org/components/3.18.x/azure-servicebus-component.html#_endpoint_query_option_tokenCredential]
> camel-azure-eventhubs: Add support for Azure-AD authentication
> --
>
> Key: CAMEL-18451
> URL: https://issues.apache.org/jira/browse/CAMEL-18451
> Project: Camel
> Issue Type: Improvement
> Components: camel-azure-eventhubs
>Affects Versions: 3.18.1
>Reporter: Babak Vahdat
>Assignee: Babak Vahdat
>Priority: Minor
> Fix For: 3.19.0
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18451) camel-azure-eventhubs: Add support for Azure-AD authentication
[
https://issues.apache.org/jira/browse/CAMEL-18451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600636#comment-17600636
]
Babak Vahdat edited comment on CAMEL-18451 at 9/6/22 7:26 AM:
--
- {{{}camel-azure-servicebus{}}}: has already got that (explicit) support.
- {{{}camel-azure-cosmosdb{}}}: has got that (implicitly) through the
{{cosmosAsyncClient}} option which would do the job both for the consumer as
well as producer.
- {{{}camel-{}}}{{{}azure-storage-blob{}}}/
{{{}camel-{}}}{{{}azure-storage-datalake{}}}/
{{{}camel-azure-{}}}{{{}storage-queue{}}}: the same as
{{{}camel-{}}}{{{}azure-cosmosdb {}}}through their {{serviceClient}} option.
That being said, I could be wrong and this needs to be verified first through
the corresponding integration tests which you would need your own azure
subscription for. And before integration testing, the corresponding resources
need to be configured to be accessible through Azure-AD authentication.
Something to be done through the Azure-Portal interface.
For 2) and 3) it would be nice to have this support explicitly (not implicitly)
then that required dependency (with the right version) for Azure-AD would be
already there for the users:
[https://github.com/apache/camel/blob/camel-3.18.2/components/camel-azure/camel-azure-servicebus/pom.xml#L56-L60]
And all they would need to provide is to bind a single {{TokenCredentail}} into
the registry:
[https://camel.apache.org/components/3.18.x/azure-servicebus-component.html#_endpoint_query_option_tokenCredential]
was (Author: bvahdat):
- {{{}camel-azure-servicebus{}}}: has already got that (explicit) support.
- {{{}camel-azure-cosmosdb{}}}: has got that (implicitly) through the
{{cosmosAsyncClient}} option which would do the job both for the consumer as
well as producer.
- {{{}camel-{}}}{{{}azure-storage-blob{}}}/
{{{}camel-{}}}{{{}azure-storage-datalake{}}}/
{{{}camel-azure-{}}}{{{}storage-queue{}}}: the same as
{{{}camel-{}}}{{{}azure-cosmosdb {}}}through their {{serviceClient}} option.
That being said, I could be wrong and this needs to be verified first through
the corresponding integration tests which you would need your own azure
subscription for. And before integration testing, the corresponding resources
need to be configured to be accessible through Azure-AD authentication.
Something to be done through the Azure-Portal interface.
For 2) and 3) it would be nice to have this support explicitly (not implicitly)
then that required dependency (with the right version) for Azure-AD would be
already there for the users:
[https://github.com/apache/camel/blob/camel-3.18.2/components/camel-azure/camel-azure-servicebus/pom.xml#L56-L60]
And all they would need to provide is to bind a single {{TokenCredentail}} into
the registry:
[https://camel.apache.org/components/3.18.x/azure-servicebus-component.html#_endpoint_query_option_tokenCredential]
> camel-azure-eventhubs: Add support for Azure-AD authentication
> --
>
> Key: CAMEL-18451
> URL: https://issues.apache.org/jira/browse/CAMEL-18451
> Project: Camel
> Issue Type: Improvement
> Components: camel-azure-eventhubs
>Affects Versions: 3.18.1
>Reporter: Babak Vahdat
>Assignee: Babak Vahdat
>Priority: Minor
> Fix For: 3.19.0
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18451) camel-azure-eventhubs: Add support for Azure-AD authentication
[
https://issues.apache.org/jira/browse/CAMEL-18451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600636#comment-17600636
]
Babak Vahdat edited comment on CAMEL-18451 at 9/6/22 7:25 AM:
--
- {{{}camel-azure-servicebus{}}}: has already got that (explicit) support.
- {{{}camel-azure-cosmosdb{}}}: has got that (implicitly) through the
{{cosmosAsyncClient}} option which would do the job both for the consumer as
well as producer.
- {{{}camel-{}}}{{{}azure-storage-blob{}}}/
{{{}camel-{}}}{{{}azure-storage-datalake{}}}/
{{{}camel-azure-{}}}{{{}storage-queue{}}}: the same as
{{{}camel-{}}}{{{}azure-cosmosdb {}}}through their {{serviceClient}} option.
That being said, I could be wrong and this needs to be verified first through
the corresponding integration tests which you would need your own azure
subscription for. And before integration testing, the corresponding resources
need to be configured to be accessible through Azure-AD authentication.
Something to be done through the Azure-Portal interface.
For 2) and 3) it would be nice to have this support explicitly (not implicitly)
then that required dependency (with the right version) for Azure-AD would be
already there for the users:
[https://github.com/apache/camel/blob/camel-3.18.2/components/camel-azure/camel-azure-servicebus/pom.xml#L56-L60]
And all they would need to provide is to bind a single {{TokenCredentail}} into
the registry:
[https://camel.apache.org/components/3.18.x/azure-servicebus-component.html#_endpoint_query_option_tokenCredential]
was (Author: bvahdat):
- {{camel-azure-servicebus}}: has already got that (explicit) support.
- {{azure-cosmosdb-component}}: has got that (implicitly) through the
{{cosmosAsyncClient}} option which would do the job both for the consumer as
well as producer.
- {{azure-storage-blob-component}} / {{azure-storage-datalake-component}} /
{{azure-storage-queue-component}}: the same as {{azure-cosmosdb-component}}
through their {{serviceClient}} option.
That being said, I could be wrong and this needs to be verified first through
the corresponding integration tests which you would need your own azure
subscription for. And before integration testing, the corresponding resources
need to be configured to be accessible through Azure-AD authentication.
Something to be done through the Azure-Portal interface.
For 2) and 3) it would be nice to have this support explicitly (not implicitly)
then that required dependency (with the right version) for Azure-AD would be
already there for the users:
https://github.com/apache/camel/blob/camel-3.18.2/components/camel-azure/camel-azure-servicebus/pom.xml#L56-L60
And all they would need to provide is to bind a single {{TokenCredentail}} into
the registry:
https://camel.apache.org/components/3.18.x/azure-servicebus-component.html#_endpoint_query_option_tokenCredential
> camel-azure-eventhubs: Add support for Azure-AD authentication
> --
>
> Key: CAMEL-18451
> URL: https://issues.apache.org/jira/browse/CAMEL-18451
> Project: Camel
> Issue Type: Improvement
> Components: camel-azure-eventhubs
>Affects Versions: 3.18.1
>Reporter: Babak Vahdat
>Assignee: Babak Vahdat
>Priority: Minor
> Fix For: 3.19.0
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18451) camel-azure-eventhubs: Add support for Azure-AD authentication
[
https://issues.apache.org/jira/browse/CAMEL-18451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600636#comment-17600636
]
Babak Vahdat commented on CAMEL-18451:
--
- {{camel-azure-servicebus}}: has already got that (explicit) support.
- {{azure-cosmosdb-component}}: has got that (implicitly) through the
{{cosmosAsyncClient}} option which would do the job both for the consumer as
well as producer.
- {{azure-storage-blob-component}} / {{azure-storage-datalake-component}} /
{{azure-storage-queue-component}}: the same as {{azure-cosmosdb-component}}
through their {{serviceClient}} option.
That being said, I could be wrong and this needs to be verified first through
the corresponding integration tests which you would need your own azure
subscription for. And before integration testing, the corresponding resources
need to be configured to be accessible through Azure-AD authentication.
Something to be done through the Azure-Portal interface.
For 2) and 3) it would be nice to have this support explicitly (not implicitly)
then that required dependency (with the right version) for Azure-AD would be
already there for the users:
https://github.com/apache/camel/blob/camel-3.18.2/components/camel-azure/camel-azure-servicebus/pom.xml#L56-L60
And all they would need to provide is to bind a single {{TokenCredentail}} into
the registry:
https://camel.apache.org/components/3.18.x/azure-servicebus-component.html#_endpoint_query_option_tokenCredential
> camel-azure-eventhubs: Add support for Azure-AD authentication
> --
>
> Key: CAMEL-18451
> URL: https://issues.apache.org/jira/browse/CAMEL-18451
> Project: Camel
> Issue Type: Improvement
> Components: camel-azure-eventhubs
>Affects Versions: 3.18.1
>Reporter: Babak Vahdat
>Assignee: Babak Vahdat
>Priority: Minor
> Fix For: 3.19.0
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18451) camel-azure-eventhubs: Add support for Azure-AD authentication
[ https://issues.apache.org/jira/browse/CAMEL-18451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat updated CAMEL-18451: - Fix Version/s: (was: 3.18.2) > camel-azure-eventhubs: Add support for Azure-AD authentication > -- > > Key: CAMEL-18451 > URL: https://issues.apache.org/jira/browse/CAMEL-18451 > Project: Camel > Issue Type: Improvement > Components: camel-azure-eventhubs >Affects Versions: 3.18.1 >Reporter: Babak Vahdat >Assignee: Babak Vahdat >Priority: Minor > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18452) Integrate azure-sdk-bom in a non-conflicting manner
[
https://issues.apache.org/jira/browse/CAMEL-18452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Babak Vahdat updated CAMEL-18452:
-
Fix Version/s: (was: 3.18.2)
> Integrate azure-sdk-bom in a non-conflicting manner
> ---
>
> Key: CAMEL-18452
> URL: https://issues.apache.org/jira/browse/CAMEL-18452
> Project: Camel
> Issue Type: Task
> Components: camel-azure
>Affects Versions: 3.18.1
>Reporter: Babak Vahdat
>Assignee: Babak Vahdat
>Priority: Minor
> Fix For: 3.19.0
>
>
> While working on CAMEL-18451 I ran into a conflicting Azure dependency issue.
> To reproduce it _just_ add the following dependency to
> {{camel-azure-eventhubs}} POM _without any_ other additional changes
> whatsoever:
> {code:java}
>
> com.azure
> azure-identity
> ${azure-identity-version}
>
> {code}
> and the integration test execution as mentioned
> [here|https://camel.apache.org/components/3.18.x/azure-eventhubs-component.html#_development_notes_important]
> will hang forever until it time outs through the {{maven-failsafe-plugin}}.
> This is because currently we have the following dependency versions on the
> main branch:
> {code:java}
> 5.11.2
> 1.5.1
> {code}
> The currently used {{azure-eventhubs}} version belongs to the BOM:
> [https://mvnrepository.com/artifact/com.azure/azure-sdk-bom/1.2.1]
> Whereas the current {{azure-identity}} version belongs to:
> [https://mvnrepository.com/artifact/com.azure/azure-sdk-bom/1.2.2]
> Each having potentially incompatible / non-matching own transitive dependency
> versions causing some sort of deadlock behaviour at runtime as explained
> above.
> We better need to make sure that whatever {{azure-XXX}} dependencies we have
> belong to the _same_ {{azure-sdk-bom}} version.
> I think it's possible to make use of {{azure-sdk-bom}} BOM in a
> non-conflicting manner.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18452) Integrate azure-sdk-bom in a non-conflicting manner
[
https://issues.apache.org/jira/browse/CAMEL-18452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Babak Vahdat resolved CAMEL-18452.
--
Resolution: Fixed
> Integrate azure-sdk-bom in a non-conflicting manner
> ---
>
> Key: CAMEL-18452
> URL: https://issues.apache.org/jira/browse/CAMEL-18452
> Project: Camel
> Issue Type: Task
> Components: camel-azure
>Affects Versions: 3.18.1
>Reporter: Babak Vahdat
>Assignee: Babak Vahdat
>Priority: Minor
> Fix For: 3.18.2, 3.19.0
>
>
> While working on CAMEL-18451 I ran into a conflicting Azure dependency issue.
> To reproduce it _just_ add the following dependency to
> {{camel-azure-eventhubs}} POM _without any_ other additional changes
> whatsoever:
> {code:java}
>
> com.azure
> azure-identity
> ${azure-identity-version}
>
> {code}
> and the integration test execution as mentioned
> [here|https://camel.apache.org/components/3.18.x/azure-eventhubs-component.html#_development_notes_important]
> will hang forever until it time outs through the {{maven-failsafe-plugin}}.
> This is because currently we have the following dependency versions on the
> main branch:
> {code:java}
> 5.11.2
> 1.5.1
> {code}
> The currently used {{azure-eventhubs}} version belongs to the BOM:
> [https://mvnrepository.com/artifact/com.azure/azure-sdk-bom/1.2.1]
> Whereas the current {{azure-identity}} version belongs to:
> [https://mvnrepository.com/artifact/com.azure/azure-sdk-bom/1.2.2]
> Each having potentially incompatible / non-matching own transitive dependency
> versions causing some sort of deadlock behaviour at runtime as explained
> above.
> We better need to make sure that whatever {{azure-XXX}} dependencies we have
> belong to the _same_ {{azure-sdk-bom}} version.
> I think it's possible to make use of {{azure-sdk-bom}} BOM in a
> non-conflicting manner.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18452) Integrate azure-sdk-bom in a non-conflicting manner
[
https://issues.apache.org/jira/browse/CAMEL-18452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Babak Vahdat updated CAMEL-18452:
-
Summary: Integrate azure-sdk-bom in a non-conflicting manner (was:
integrate azure-sdk-bom in a non-conflicting manner)
> Integrate azure-sdk-bom in a non-conflicting manner
> ---
>
> Key: CAMEL-18452
> URL: https://issues.apache.org/jira/browse/CAMEL-18452
> Project: Camel
> Issue Type: Task
> Components: camel-azure
>Affects Versions: 3.18.1
>Reporter: Babak Vahdat
>Assignee: Babak Vahdat
>Priority: Minor
> Fix For: 3.18.2, 3.19.0
>
>
> While working on CAMEL-18451 I ran into a conflicting Azure dependency issue.
> To reproduce it _just_ add the following dependency to
> {{camel-azure-eventhubs}} POM _without any_ other additional changes
> whatsoever:
> {code:java}
>
> com.azure
> azure-identity
> ${azure-identity-version}
>
> {code}
> and the integration test execution as mentioned
> [here|https://camel.apache.org/components/3.18.x/azure-eventhubs-component.html#_development_notes_important]
> will hang forever until it time outs through the {{maven-failsafe-plugin}}.
> This is because currently we have the following dependency versions on the
> main branch:
> {code:java}
> 5.11.2
> 1.5.1
> {code}
> The currently used {{azure-eventhubs}} version belongs to the BOM:
> [https://mvnrepository.com/artifact/com.azure/azure-sdk-bom/1.2.1]
> Whereas the current {{azure-identity}} version belongs to:
> [https://mvnrepository.com/artifact/com.azure/azure-sdk-bom/1.2.2]
> Each having potentially incompatible / non-matching own transitive dependency
> versions causing some sort of deadlock behaviour at runtime as explained
> above.
> We better need to make sure that whatever {{azure-XXX}} dependencies we have
> belong to the _same_ {{azure-sdk-bom}} version.
> I think it's possible to make use of {{azure-sdk-bom}} BOM in a
> non-conflicting manner.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18452) integrate azure-sdk-bom in a non-conflicting manner
[
https://issues.apache.org/jira/browse/CAMEL-18452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Babak Vahdat updated CAMEL-18452:
-
Description:
While working on CAMEL-18451 I ran into a conflicting Azure dependency issue.
To reproduce it _just_ add the following dependency to
{{camel-azure-eventhubs}} POM _without any_ other additional changes whatsoever:
{code:java}
com.azure
azure-identity
${azure-identity-version}
{code}
and the integration test execution as mentioned
[here|https://camel.apache.org/components/3.18.x/azure-eventhubs-component.html#_development_notes_important]
will hang forever until it time outs through the {{maven-failsafe-plugin}}.
This is because currently we have the following dependency versions on the main
branch:
{code:java}
5.11.2
1.5.1
{code}
The currently used {{azure-eventhubs}} version belongs to the BOM:
[https://mvnrepository.com/artifact/com.azure/azure-sdk-bom/1.2.1]
Whereas the current {{azure-identity}} version belongs to:
[https://mvnrepository.com/artifact/com.azure/azure-sdk-bom/1.2.2]
Each having potentially incompatible / non-matching own transitive dependency
versions causing some sort of deadlock behaviour at runtime as explained above.
We better need to make sure that whatever {{azure-XXX}} dependencies we have
belong to the _same_ {{azure-sdk-bom}} version.
I think it's possible to make use of {{azure-sdk-bom}} BOM in a non-conflicting
manner.
was:
While working on CAMEL-18451 I ran into a conflicting Azure dependency issue.
To reproduce it _just_ add the following dependency to
{{camel-azure-eventhubs}} POM _without any_ other additional changes whatsoever:
{code:java}
com.azure
azure-identity
${azure-identity-version}
{code}
and the integration test execution as mentioned
[here|https://camel.apache.org/components/3.18.x/azure-eventhubs-component.html#_development_notes_important]
will hang forever until it time outs through the
{{{}maven-failesafe-plugin{}}}.
This is because currently we have the following dependency versions on the main
branch:
{code:java}
5.11.2
1.5.1
{code}
The currently used {{azure-eventhubs}} version belongs to the BOM:
[https://mvnrepository.com/artifact/com.azure/azure-sdk-bom/1.2.1]
Whereas the current {{azure-identity}} version belongs to:
[https://mvnrepository.com/artifact/com.azure/azure-sdk-bom/1.2.2]
Each having potentially incompatible / non-matching own transitive dependency
versions causing some sort of deadlock behaviour at runtime as explained above.
We better need to make sure that whatever {{azure-XXX}} dependencies we have
belong to the _same_ {{azure-sdk-bom}} version.
I think it's possible to make use of {{azure-sdk-bom}} BOM in a non-conflicting
manner.
> integrate azure-sdk-bom in a non-conflicting manner
> ---
>
> Key: CAMEL-18452
> URL: https://issues.apache.org/jira/browse/CAMEL-18452
> Project: Camel
> Issue Type: Task
> Components: camel-azure
>Affects Versions: 3.18.1
>Reporter: Babak Vahdat
>Assignee: Babak Vahdat
>Priority: Minor
> Fix For: 3.18.2, 3.19.0
>
>
> While working on CAMEL-18451 I ran into a conflicting Azure dependency issue.
> To reproduce it _just_ add the following dependency to
> {{camel-azure-eventhubs}} POM _without any_ other additional changes
> whatsoever:
> {code:java}
>
> com.azure
> azure-identity
> ${azure-identity-version}
>
> {code}
> and the integration test execution as mentioned
> [here|https://camel.apache.org/components/3.18.x/azure-eventhubs-component.html#_development_notes_important]
> will hang forever until it time outs through the {{maven-failsafe-plugin}}.
> This is because currently we have the following dependency versions on the
> main branch:
> {code:java}
> 5.11.2
> 1.5.1
> {code}
> The currently used {{azure-eventhubs}} version belongs to the BOM:
> [https://mvnrepository.com/artifact/com.azure/azure-sdk-bom/1.2.1]
> Whereas the current {{azure-identity}} version belongs to:
> [https://mvnrepository.com/artifact/com.azure/azure-sdk-bom/1.2.2]
> Each having potentially incompatible / non-matching own transitive dependency
> versions causing some sort of deadlock behaviour at runtime as explained
> above.
> We better need to make sure that whatever {{azure-XXX}} dependencies we have
> belong to the _same_ {{azure-sdk-bom}} version.
> I think it's possible to make use of {{azure-sdk-bom}} BOM in a
> non-conflicting manner.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-18452) integrate azure-sdk-bom in a non-conflicting manner
Babak Vahdat created CAMEL-18452:
Summary: integrate azure-sdk-bom in a non-conflicting manner
Key: CAMEL-18452
URL: https://issues.apache.org/jira/browse/CAMEL-18452
Project: Camel
Issue Type: Task
Components: camel-azure
Affects Versions: 3.18.1
Reporter: Babak Vahdat
Assignee: Babak Vahdat
Fix For: 3.18.2, 3.19.0
While working on CAMEL-18451 I ran into a conflicting Azure dependency issue.
To reproduce it _just_ add the following dependency to
{{camel-azure-eventhubs}} POM _without any_ other additional changes whatsoever:
{code:java}
com.azure
azure-identity
${azure-identity-version}
{code}
and the integration test execution as mentioned
[here|https://camel.apache.org/components/3.18.x/azure-eventhubs-component.html#_development_notes_important]
will hang forever until it time outs through the
{{{}maven-failesafe-plugin{}}}.
This is because currently we have the following dependency versions on the main
branch:
{code:java}
5.11.2
1.5.1
{code}
The currently used {{azure-eventhubs}} version belongs to the BOM:
[https://mvnrepository.com/artifact/com.azure/azure-sdk-bom/1.2.1]
Whereas the current {{azure-identity}} version belongs to:
[https://mvnrepository.com/artifact/com.azure/azure-sdk-bom/1.2.2]
Each having potentially incompatible / non-matching own transitive dependency
versions causing some sort of deadlock behaviour at runtime as explained above.
We better need to make sure that whatever {{azure-XXX}} dependencies we have
belong to the _same_ {{azure-sdk-bom}} version.
I think it's possible to make use of {{azure-sdk-bom}} BOM in a non-conflicting
manner.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-18451) camel-azure-eventhubs: Add support for Azure-AD authentication
Babak Vahdat created CAMEL-18451: Summary: camel-azure-eventhubs: Add support for Azure-AD authentication Key: CAMEL-18451 URL: https://issues.apache.org/jira/browse/CAMEL-18451 Project: Camel Issue Type: Improvement Components: camel-azure-eventhubs Affects Versions: 3.18.1 Reporter: Babak Vahdat Assignee: Babak Vahdat Fix For: 3.18.2, 3.19.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18250) When a Call to Salesforce timeouts then we have Exchange.HTTP_RESPONSE_CODE Exchange Header set as "0"
Babak Vahdat created CAMEL-18250: Summary: When a Call to Salesforce timeouts then we have Exchange.HTTP_RESPONSE_CODE Exchange Header set as "0" Key: CAMEL-18250 URL: https://issues.apache.org/jira/browse/CAMEL-18250 Project: Camel Issue Type: Bug Components: camel-salesforce Affects Versions: 3.17.0 Reporter: Babak Vahdat Assignee: Babak Vahdat Fix For: 3.18.0 As because then there is an implicit 0 (as int) to "0" (as string) conversion happening. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18068) Upgrade Azure dependencies based on com.azure:azure-sdk-bom:1.2.1
[ https://issues.apache.org/jira/browse/CAMEL-18068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat resolved CAMEL-18068. -- Resolution: Fixed > Upgrade Azure dependencies based on com.azure:azure-sdk-bom:1.2.1 > - > > Key: CAMEL-18068 > URL: https://issues.apache.org/jira/browse/CAMEL-18068 > Project: Camel > Issue Type: Task > Components: camel-azure >Reporter: Babak Vahdat >Assignee: Babak Vahdat >Priority: Minor > Fix For: 3.17.0 > > > https://mvnrepository.com/artifact/com.azure/azure-sdk-bom/1.2.1 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (CAMEL-18068) Upgrade Azure dependencies based on com.azure:azure-sdk-bom:1.2.1
Babak Vahdat created CAMEL-18068: Summary: Upgrade Azure dependencies based on com.azure:azure-sdk-bom:1.2.1 Key: CAMEL-18068 URL: https://issues.apache.org/jira/browse/CAMEL-18068 Project: Camel Issue Type: Task Components: camel-azure Reporter: Babak Vahdat Assignee: Babak Vahdat Fix For: 3.17.0 https://mvnrepository.com/artifact/com.azure/azure-sdk-bom/1.2.1 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (CAMEL-18055) Create tracing SpanDecorator for ServiceBusComponent
[ https://issues.apache.org/jira/browse/CAMEL-18055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat resolved CAMEL-18055. -- Resolution: Fixed > Create tracing SpanDecorator for ServiceBusComponent > > > Key: CAMEL-18055 > URL: https://issues.apache.org/jira/browse/CAMEL-18055 > Project: Camel > Issue Type: Task > Components: camel-tracing >Reporter: Babak Vahdat >Assignee: Babak Vahdat >Priority: Minor > Fix For: 3.17.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (CAMEL-18055) Create tracing SpanDecorator for ServiceBusComponent
Babak Vahdat created CAMEL-18055: Summary: Create tracing SpanDecorator for ServiceBusComponent Key: CAMEL-18055 URL: https://issues.apache.org/jira/browse/CAMEL-18055 Project: Camel Issue Type: Task Components: camel-tracing Reporter: Babak Vahdat Assignee: Babak Vahdat Fix For: 3.17.0 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (CAMEL-17515) Provide an option to mark Camel readiness as DOWN during graceful shutdown
[ https://issues.apache.org/jira/browse/CAMEL-17515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat updated CAMEL-17515: - Description: https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/.E2.9C.94.20timout.20of.20DefaultShutdownStrategy (was: https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/timout.20of.20DefaultShutdownStrategy) > Provide an option to mark Camel readiness as DOWN during graceful shutdown > -- > > Key: CAMEL-17515 > URL: https://issues.apache.org/jira/browse/CAMEL-17515 > Project: Camel > Issue Type: Improvement >Affects Versions: 3.14.0 >Reporter: Babak Vahdat >Priority: Minor > > https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/.E2.9C.94.20timout.20of.20DefaultShutdownStrategy -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17886) MockValueBuilder behaves false positive
Babak Vahdat created CAMEL-17886:
Summary: MockValueBuilder behaves false positive
Key: CAMEL-17886
URL: https://issues.apache.org/jira/browse/CAMEL-17886
Project: Camel
Issue Type: Bug
Components: camel-mock
Affects Versions: 3.16.0
Reporter: Babak Vahdat
If I change the following line:
https://github.com/apache/camel/blob/camel-3.16.0/components/camel-mail/src/test/java/org/apache/camel/component/mail/RawMailMessageTest.java#L100
To:
{code}
mock.expectedBodyReceived().body().isNull();
mock.expectedBodyReceived().body().isEqualTo(new Object());
{code}
Then the test would still pass.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (CAMEL-17515) Provide an option to mark Camel readiness as DOWN during graceful shutdown
[ https://issues.apache.org/jira/browse/CAMEL-17515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat updated CAMEL-17515: - Priority: Minor (was: Major) > Provide an option to mark Camel readiness as DOWN during graceful shutdown > -- > > Key: CAMEL-17515 > URL: https://issues.apache.org/jira/browse/CAMEL-17515 > Project: Camel > Issue Type: Improvement >Affects Versions: 3.14.0 >Reporter: Babak Vahdat >Priority: Minor > > https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/timout.20of.20DefaultShutdownStrategy -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17515) Provide an option to mark Camel readiness as DOWN during graceful shutdown
[
https://issues.apache.org/jira/browse/CAMEL-17515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478819#comment-17478819
]
Babak Vahdat commented on CAMEL-17515:
--
My current workaround is:
{{export CAMEL_MAIN_SHUTDOWNTIMEOUT=1}}
> Provide an option to mark Camel readiness as DOWN during graceful shutdown
> --
>
> Key: CAMEL-17515
> URL: https://issues.apache.org/jira/browse/CAMEL-17515
> Project: Camel
> Issue Type: Improvement
>Affects Versions: 3.14.0
>Reporter: Babak Vahdat
>Priority: Major
>
> https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/timout.20of.20DefaultShutdownStrategy
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (CAMEL-17515) Provide an option to mark Camel readiness as DOWN during graceful shutdown
[ https://issues.apache.org/jira/browse/CAMEL-17515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat updated CAMEL-17515: - Summary: Provide an option to mark Camel readiness as DOWN during graceful shutdown (was: Provide an option to mark Camel readiness as DOWN as soon as e.g. when a route gets stopped) > Provide an option to mark Camel readiness as DOWN during graceful shutdown > -- > > Key: CAMEL-17515 > URL: https://issues.apache.org/jira/browse/CAMEL-17515 > Project: Camel > Issue Type: Improvement >Affects Versions: 3.14.0 >Reporter: Babak Vahdat >Priority: Major > > https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/timout.20of.20DefaultShutdownStrategy -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17515) Provide an option to mark Camel readiness as DOWN as soon as e.g. when a route gets stopped
[ https://issues.apache.org/jira/browse/CAMEL-17515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat updated CAMEL-17515: - Summary: Provide an option to mark Camel readiness as DOWN as soon as e.g. when a route gets stopped (was: Provide an option to mark Camel readiness as DOWN as soon as when a route gets stopped) > Provide an option to mark Camel readiness as DOWN as soon as e.g. when a > route gets stopped > --- > > Key: CAMEL-17515 > URL: https://issues.apache.org/jira/browse/CAMEL-17515 > Project: Camel > Issue Type: Improvement >Affects Versions: 3.14.0 >Reporter: Babak Vahdat >Priority: Major > > https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/timout.20of.20DefaultShutdownStrategy -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17515) Provide an option to mark Camel readiness as DOWN as soon as when a route gets stopped
Babak Vahdat created CAMEL-17515: Summary: Provide an option to mark Camel readiness as DOWN as soon as when a route gets stopped Key: CAMEL-17515 URL: https://issues.apache.org/jira/browse/CAMEL-17515 Project: Camel Issue Type: Improvement Affects Versions: 3.14.0 Reporter: Babak Vahdat https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/timout.20of.20DefaultShutdownStrategy -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-16244) Multiple consumers for the same endpoint using camel-restdsl-openapi-plugin
[
https://issues.apache.org/jira/browse/CAMEL-16244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17292124#comment-17292124
]
Babak Vahdat commented on CAMEL-16244:
--
I confirm that's fixed using the latest {{3.9.0-SNAPSHOT}} codebase with
{{restConfiguration}} being turned off, thanks!
> Multiple consumers for the same endpoint using camel-restdsl-openapi-plugin
> ---
>
> Key: CAMEL-16244
> URL: https://issues.apache.org/jira/browse/CAMEL-16244
> Project: Camel
> Issue Type: Bug
> Components: camel-rest-openapi
>Affects Versions: 3.8.0
>Reporter: Babak Vahdat
>Priority: Major
> Fix For: 3.9.0
>
>
> See the following repo as reproducer:
> [https://github.com/bvahdat/camel-rest-multiple-consumer-bug]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (CAMEL-16244) Multiple consumers for the same endpoint using camel-restdsl-openapi-plugin
[ https://issues.apache.org/jira/browse/CAMEL-16244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat reassigned CAMEL-16244: Assignee: Claus Ibsen > Multiple consumers for the same endpoint using camel-restdsl-openapi-plugin > --- > > Key: CAMEL-16244 > URL: https://issues.apache.org/jira/browse/CAMEL-16244 > Project: Camel > Issue Type: Bug > Components: camel-rest-openapi >Affects Versions: 3.8.0 >Reporter: Babak Vahdat >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.9.0 > > > See the following repo as reproducer: > [https://github.com/bvahdat/camel-rest-multiple-consumer-bug] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-16041) The managed dependency version through Camel Spring Boot BOM for com.google.guava:guava is from 2015
[
https://issues.apache.org/jira/browse/CAMEL-16041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Babak Vahdat resolved CAMEL-16041.
--
Resolution: Fixed
As Claus has already suggested above, using the BOM {{camel-spring-boot-bom}}
instead of {{camel-spring-boot-dependencies}} doesn't pull in the guava version
anymore.
> The managed dependency version through Camel Spring Boot BOM for
> com.google.guava:guava is from 2015
>
>
> Key: CAMEL-16041
> URL: https://issues.apache.org/jira/browse/CAMEL-16041
> Project: Camel
> Issue Type: Task
>Affects Versions: 3.7.0
>Reporter: Babak Vahdat
>Priority: Minor
> Fix For: 3.8.0
>
>
> Consider the following sample application POM:
> {code:xml}
>
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd;>
> 4.0.0
> com.foo
> bar
> 0.1.0-SNAPSHOT
>
>
>
>
> org.apache.camel.springboot
> camel-spring-boot-bom
> 3.7.0
> pom
> import
>
>
>
>
>
> com.google.guava
> guava
>
>
>
> {code}
> Then you would inherit the managed dependency version
> [19.0|https://search.maven.org/artifact/com.google.guava/guava/19.0/bundle]
> released in {{2015}}:
> {code:java|title=Bar.java|borderStyle=solid}
> $> mvn dependency:tree
> [INFO] Scanning for projects...
> [INFO]
> [INFO] < com.foo:bar
> >-
> [INFO] Building bar 0.1.0-SNAPSHOT
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ bar ---
> [INFO] com.foo:bar:jar:0.1.0-SNAPSHOT
> [INFO] \- com.google.guava:guava:jar:19.0:compile
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 1.190 s
> [INFO] Finished at: 2021-01-15T08:19:47+01:00
> [INFO]
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-16041) The managed dependency version through Camel Spring Boot BOM for com.google.guava:guava is from 2015
[
https://issues.apache.org/jira/browse/CAMEL-16041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Babak Vahdat updated CAMEL-16041:
-
Fix Version/s: 3.8.0
> The managed dependency version through Camel Spring Boot BOM for
> com.google.guava:guava is from 2015
>
>
> Key: CAMEL-16041
> URL: https://issues.apache.org/jira/browse/CAMEL-16041
> Project: Camel
> Issue Type: Task
>Affects Versions: 3.7.0
>Reporter: Babak Vahdat
>Priority: Minor
> Fix For: 3.8.0
>
>
> Consider the following sample application POM:
> {code:xml}
>
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd;>
> 4.0.0
> com.foo
> bar
> 0.1.0-SNAPSHOT
>
>
>
>
> org.apache.camel.springboot
> camel-spring-boot-bom
> 3.7.0
> pom
> import
>
>
>
>
>
> com.google.guava
> guava
>
>
>
> {code}
> Then you would inherit the managed dependency version
> [19.0|https://search.maven.org/artifact/com.google.guava/guava/19.0/bundle]
> released in {{2015}}:
> {code:java|title=Bar.java|borderStyle=solid}
> $> mvn dependency:tree
> [INFO] Scanning for projects...
> [INFO]
> [INFO] < com.foo:bar
> >-
> [INFO] Building bar 0.1.0-SNAPSHOT
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ bar ---
> [INFO] com.foo:bar:jar:0.1.0-SNAPSHOT
> [INFO] \- com.google.guava:guava:jar:19.0:compile
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 1.190 s
> [INFO] Finished at: 2021-01-15T08:19:47+01:00
> [INFO]
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-16244) Multiple consumers for the same endpoint using camel-restdsl-openapi-plugin
[ https://issues.apache.org/jira/browse/CAMEL-16244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17287989#comment-17287989 ] Babak Vahdat commented on CAMEL-16244: -- I assume this's a side effect of routes not being lazily started anymore: [https://camel.apache.org/manual/latest/camel-3x-upgrade-guide-3_8.html#_route_startup_procedure_change] > Multiple consumers for the same endpoint using camel-restdsl-openapi-plugin > --- > > Key: CAMEL-16244 > URL: https://issues.apache.org/jira/browse/CAMEL-16244 > Project: Camel > Issue Type: Bug > Components: camel-rest-openapi >Affects Versions: 3.8.0 >Reporter: Babak Vahdat >Priority: Major > > See the following repo as reproducer: > [https://github.com/bvahdat/camel-rest-multiple-consumer-bug] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-16244) Multiple consumers for the same endpoint using camel-restdsl-openapi-plugin
Babak Vahdat created CAMEL-16244: Summary: Multiple consumers for the same endpoint using camel-restdsl-openapi-plugin Key: CAMEL-16244 URL: https://issues.apache.org/jira/browse/CAMEL-16244 Project: Camel Issue Type: Bug Components: camel-rest-openapi Affects Versions: 3.8.0 Reporter: Babak Vahdat See the following repo as reproducer: [https://github.com/bvahdat/camel-rest-multiple-consumer-bug] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16041) The managed dependency version through Camel Spring Boot BOM for com.google.guava:guava is from 2015
[
https://issues.apache.org/jira/browse/CAMEL-16041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17269666#comment-17269666
]
Babak Vahdat commented on CAMEL-16041:
--
I just verified {{3.7.1}} and the behaviour is the same. I guess CAMEL-15428
and CAMEL-16055 are somehow relevant in this content.
> The managed dependency version through Camel Spring Boot BOM for
> com.google.guava:guava is from 2015
>
>
> Key: CAMEL-16041
> URL: https://issues.apache.org/jira/browse/CAMEL-16041
> Project: Camel
> Issue Type: Task
>Affects Versions: 3.7.0
>Reporter: Babak Vahdat
>Priority: Minor
>
> Consider the following sample application POM:
> {code:xml}
>
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd;>
> 4.0.0
> com.foo
> bar
> 0.1.0-SNAPSHOT
>
>
>
>
> org.apache.camel.springboot
> camel-spring-boot-bom
> 3.7.0
> pom
> import
>
>
>
>
>
> com.google.guava
> guava
>
>
>
> {code}
> Then you would inherit the managed dependency version
> [19.0|https://search.maven.org/artifact/com.google.guava/guava/19.0/bundle]
> released in {{2015}}:
> {code:java|title=Bar.java|borderStyle=solid}
> $> mvn dependency:tree
> [INFO] Scanning for projects...
> [INFO]
> [INFO] < com.foo:bar
> >-
> [INFO] Building bar 0.1.0-SNAPSHOT
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ bar ---
> [INFO] com.foo:bar:jar:0.1.0-SNAPSHOT
> [INFO] \- com.google.guava:guava:jar:19.0:compile
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 1.190 s
> [INFO] Finished at: 2021-01-15T08:19:47+01:00
> [INFO]
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-15998) Camel-Github: Better structure for consumer returned object
[ https://issues.apache.org/jira/browse/CAMEL-15998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17266083#comment-17266083 ] Babak Vahdat commented on CAMEL-15998: -- Hi I think we override one set header value with another one: [https://github.com/apache/camel/blob/bd790e5afb5bd3d4fbe294138d4b0be111717847/components/camel-github/src/main/java/org/apache/camel/component/github/consumer/CommitConsumer.java#L75-L76] Maybe it needs another header name for that? And IMHO the downside of these changes is that as the github and / or git APIs evolve through time with more properties in those exposed POJOs of them then we continuously need to add them to the corresponding new headers as the time passes by. This however would not be necessary in case of the original implementation. > Camel-Github: Better structure for consumer returned object > --- > > Key: CAMEL-15998 > URL: https://issues.apache.org/jira/browse/CAMEL-15998 > Project: Camel > Issue Type: Improvement > Components: camel-git >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.8.0 > > > We can specify something more through headers. The problem is similar to > camel-git, we need to have a plain type as body and enrich the information > through headers. It will be much more easier to use, instead of having to > deal with egit pojos -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16041) The managed dependency version through Camel Spring Boot BOM for com.google.guava:guava is from 2015
[
https://issues.apache.org/jira/browse/CAMEL-16041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17265800#comment-17265800
]
Babak Vahdat commented on CAMEL-16041:
--
{quote}
Yeah try with 3.7.1 as there was a problem with the parent pom.xml being pulled
in
{quote}
Thanks will try as soon as it's out and would close this ticket accordingly.
> The managed dependency version through Camel Spring Boot BOM for
> com.google.guava:guava is from 2015
>
>
> Key: CAMEL-16041
> URL: https://issues.apache.org/jira/browse/CAMEL-16041
> Project: Camel
> Issue Type: Task
>Affects Versions: 3.7.0
>Reporter: Babak Vahdat
>Priority: Minor
>
> Consider the following sample application POM:
> {code:xml}
>
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd;>
> 4.0.0
> com.foo
> bar
> 0.1.0-SNAPSHOT
>
>
>
>
> org.apache.camel.springboot
> camel-spring-boot-bom
> 3.7.0
> pom
> import
>
>
>
>
>
> com.google.guava
> guava
>
>
>
> {code}
> Then you would inherit the managed dependency version
> [19.0|https://search.maven.org/artifact/com.google.guava/guava/19.0/bundle]
> released in {{2015}}:
> {code:java|title=Bar.java|borderStyle=solid}
> $> mvn dependency:tree
> [INFO] Scanning for projects...
> [INFO]
> [INFO] < com.foo:bar
> >-
> [INFO] Building bar 0.1.0-SNAPSHOT
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ bar ---
> [INFO] com.foo:bar:jar:0.1.0-SNAPSHOT
> [INFO] \- com.google.guava:guava:jar:19.0:compile
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 1.190 s
> [INFO] Finished at: 2021-01-15T08:19:47+01:00
> [INFO]
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-16041) The managed dependency version through Camel Spring Boot BOM for com.google.guava:guava is from 2015
[
https://issues.apache.org/jira/browse/CAMEL-16041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17265792#comment-17265792
]
Babak Vahdat commented on CAMEL-16041:
--
For sure as a workaround one can always use his own version to override that
old inherited managed dependency from Camel:
{code:xml}
com.google.guava
guava
${my.guava.version}
{code}
Please also note that exclusion of managed dependencies [is currently not
possible in Maven|https://github.com/apache/maven/pull/295].
And the real pain is the fact that the Maven managed dependencies have higher
precedence over the transitive ones! In our case this old version from Camel
overrided the version Wiremock [currently
uses|https://github.com/tomakehurst/wiremock/blob/28c5e6737caa7887e2070033bd361501e12ea3ee/build.gradle#L39].
And you would not even think of such a scenario until your tests start to
fail. :-(
> The managed dependency version through Camel Spring Boot BOM for
> com.google.guava:guava is from 2015
>
>
> Key: CAMEL-16041
> URL: https://issues.apache.org/jira/browse/CAMEL-16041
> Project: Camel
> Issue Type: Task
>Affects Versions: 3.7.0
>Reporter: Babak Vahdat
>Priority: Minor
>
> Consider the following sample application POM:
> {code:xml}
>
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd;>
> 4.0.0
> com.foo
> bar
> 0.1.0-SNAPSHOT
>
>
>
>
> org.apache.camel.springboot
> camel-spring-boot-bom
> 3.7.0
> pom
> import
>
>
>
>
>
> com.google.guava
> guava
>
>
>
> {code}
> Then you would inherit the managed dependency version
> [19.0|https://search.maven.org/artifact/com.google.guava/guava/19.0/bundle]
> released in {{2015}}:
> {code:java|title=Bar.java|borderStyle=solid}
> $> mvn dependency:tree
> [INFO] Scanning for projects...
> [INFO]
> [INFO] < com.foo:bar
> >-
> [INFO] Building bar 0.1.0-SNAPSHOT
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ bar ---
> [INFO] com.foo:bar:jar:0.1.0-SNAPSHOT
> [INFO] \- com.google.guava:guava:jar:19.0:compile
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 1.190 s
> [INFO] Finished at: 2021-01-15T08:19:47+01:00
> [INFO]
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-16041) The managed dependency version through Camel Spring Boot BOM for com.google.guava:guava is from 2015
[
https://issues.apache.org/jira/browse/CAMEL-16041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17265784#comment-17265784
]
Babak Vahdat commented on CAMEL-16041:
--
Thanks [~davsclaus], updated the description as it's still the same behaviour
using that {{artifactId}}.
> The managed dependency version through Camel Spring Boot BOM for
> com.google.guava:guava is from 2015
>
>
> Key: CAMEL-16041
> URL: https://issues.apache.org/jira/browse/CAMEL-16041
> Project: Camel
> Issue Type: Task
>Affects Versions: 3.7.0
>Reporter: Babak Vahdat
>Priority: Minor
>
> Consider the following sample application POM:
> {code:xml}
>
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd;>
> 4.0.0
> com.foo
> bar
> 0.1.0-SNAPSHOT
>
>
>
>
> org.apache.camel.springboot
> camel-spring-boot-bom
> 3.7.0
> pom
> import
>
>
>
>
>
> com.google.guava
> guava
>
>
>
> {code}
> Then you would inherit the managed dependency version
> [19.0|https://search.maven.org/artifact/com.google.guava/guava/19.0/bundle]
> released in {{2015}}:
> {code:java|title=Bar.java|borderStyle=solid}
> $> mvn dependency:tree
> [INFO] Scanning for projects...
> [INFO]
> [INFO] < com.foo:bar
> >-
> [INFO] Building bar 0.1.0-SNAPSHOT
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ bar ---
> [INFO] com.foo:bar:jar:0.1.0-SNAPSHOT
> [INFO] \- com.google.guava:guava:jar:19.0:compile
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 1.190 s
> [INFO] Finished at: 2021-01-15T08:19:47+01:00
> [INFO]
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-16041) The managed dependency version through Camel Spring Boot BOM for com.google.guava:guava is from 2015
[
https://issues.apache.org/jira/browse/CAMEL-16041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Babak Vahdat updated CAMEL-16041:
-
Description:
Consider the following sample application POM:
{code:xml}
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;>
4.0.0
com.foo
bar
0.1.0-SNAPSHOT
org.apache.camel.springboot
camel-spring-boot-bom
3.7.0
pom
import
com.google.guava
guava
{code}
Then you would inherit the managed dependency version
[19.0|https://search.maven.org/artifact/com.google.guava/guava/19.0/bundle]
released in {{2015}}:
{code:java|title=Bar.java|borderStyle=solid}
$> mvn dependency:tree
[INFO] Scanning for projects...
[INFO]
[INFO] < com.foo:bar >-
[INFO] Building bar 0.1.0-SNAPSHOT
[INFO] [ jar ]-
[INFO]
[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ bar ---
[INFO] com.foo:bar:jar:0.1.0-SNAPSHOT
[INFO] \- com.google.guava:guava:jar:19.0:compile
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.190 s
[INFO] Finished at: 2021-01-15T08:19:47+01:00
[INFO]
{code}
was:
Consider the following sample application POM:
{code:xml}
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;>
4.0.0
com.foo
bar
0.1.0-SNAPSHOT
org.apache.camel.springboot
camel-spring-boot-dependencies
3.7.0
pom
import
com.google.guava
guava
{code}
Then you would inherit the managed dependency version
[19.0|https://search.maven.org/artifact/com.google.guava/guava/19.0/bundle]
released in {{2015}}:
{code:title=Bar.java|borderStyle=solid}
$> mvn dependency:tree
[INFO] Scanning for projects...
[INFO]
[INFO] < com.foo:bar >-
[INFO] Building bar 0.1.0-SNAPSHOT
[INFO] [ jar ]-
[INFO]
[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ bar ---
[INFO] com.foo:bar:jar:0.1.0-SNAPSHOT
[INFO] \- com.google.guava:guava:jar:19.0:compile
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.190 s
[INFO] Finished at: 2021-01-15T08:19:47+01:00
[INFO]
{code}
> The managed dependency version through Camel Spring Boot BOM for
> com.google.guava:guava is from 2015
>
>
> Key: CAMEL-16041
> URL: https://issues.apache.org/jira/browse/CAMEL-16041
> Project: Camel
> Issue Type: Task
>Affects Versions: 3.7.0
>Reporter: Babak Vahdat
>Priority: Minor
>
> Consider the following sample application POM:
> {code:xml}
>
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd;>
> 4.0.0
> com.foo
> bar
> 0.1.0-SNAPSHOT
>
>
>
>
> org.apache.camel.springboot
> camel-spring-boot-bom
> 3.7.0
> pom
> import
>
>
>
>
>
> com.google.guava
> guava
>
>
>
> {code}
> Then you would inherit the managed dependency version
> [19.0|https://search.maven.org/artifact/com.google.guava/guava/19.0/bundle]
> released in {{2015}}:
> {code:java|title=Bar.java|borderStyle=solid}
> $> mvn dependency:tree
> [INFO] Scanning for projects...
> [INFO]
> [INFO] < com.foo:bar
> >-
> [INFO] Building bar 0.1.0-SNAPSHOT
> [INFO] [ jar
> ]-
>
[jira] [Updated] (CAMEL-16041) The managed dependency version through Camel Spring Boot BOM for com.google.guava:guava is from 2015
[
https://issues.apache.org/jira/browse/CAMEL-16041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Babak Vahdat updated CAMEL-16041:
-
Summary: The managed dependency version through Camel Spring Boot BOM for
com.google.guava:guava is from 2015 (was: The managed dependency version
through Camel BOM for com.google.guava:guava is from 2015)
> The managed dependency version through Camel Spring Boot BOM for
> com.google.guava:guava is from 2015
>
>
> Key: CAMEL-16041
> URL: https://issues.apache.org/jira/browse/CAMEL-16041
> Project: Camel
> Issue Type: Task
>Affects Versions: 3.7.0
>Reporter: Babak Vahdat
>Priority: Minor
>
> Consider the following sample application POM:
> {code:xml}
>
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd;>
> 4.0.0
> com.foo
> bar
> 0.1.0-SNAPSHOT
>
>
>
>
> org.apache.camel.springboot
> camel-spring-boot-dependencies
> 3.7.0
> pom
> import
>
>
>
>
>
> com.google.guava
> guava
>
>
>
> {code}
> Then you would inherit the managed dependency version
> [19.0|https://search.maven.org/artifact/com.google.guava/guava/19.0/bundle]
> released in {{2015}}:
> {code:title=Bar.java|borderStyle=solid}
> $> mvn dependency:tree
> [INFO] Scanning for projects...
> [INFO]
> [INFO] < com.foo:bar
> >-
> [INFO] Building bar 0.1.0-SNAPSHOT
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ bar ---
> [INFO] com.foo:bar:jar:0.1.0-SNAPSHOT
> [INFO] \- com.google.guava:guava:jar:19.0:compile
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 1.190 s
> [INFO] Finished at: 2021-01-15T08:19:47+01:00
> [INFO]
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-16041) The managed dependency version through Camel BOM for com.google.guava:guava is from 2015
Babak Vahdat created CAMEL-16041:
Summary: The managed dependency version through Camel BOM for
com.google.guava:guava is from 2015
Key: CAMEL-16041
URL: https://issues.apache.org/jira/browse/CAMEL-16041
Project: Camel
Issue Type: Task
Affects Versions: 3.7.0
Reporter: Babak Vahdat
Consider the following sample application POM:
{code:xml}
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;>
4.0.0
com.foo
bar
0.1.0-SNAPSHOT
org.apache.camel.springboot
camel-spring-boot-dependencies
3.7.0
pom
import
com.google.guava
guava
{code}
Then you would inherit the managed dependency version
[19.0|https://search.maven.org/artifact/com.google.guava/guava/19.0/bundle]
released in {{2015}}:
{code:title=Bar.java|borderStyle=solid}
$> mvn dependency:tree
[INFO] Scanning for projects...
[INFO]
[INFO] < com.foo:bar >-
[INFO] Building bar 0.1.0-SNAPSHOT
[INFO] [ jar ]-
[INFO]
[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ bar ---
[INFO] com.foo:bar:jar:0.1.0-SNAPSHOT
[INFO] \- com.google.guava:guava:jar:19.0:compile
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.190 s
[INFO] Finished at: 2021-01-15T08:19:47+01:00
[INFO]
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (CAMEL-15747) [camel-azure-strorage-blob] Regex is not supported by Consumer
[ https://issues.apache.org/jira/browse/CAMEL-15747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat closed CAMEL-15747. Resolution: Not A Problem Closing as per discussion in https://github.com/apache/camel/pull/4712 > [camel-azure-strorage-blob] Regex is not supported by Consumer > -- > > Key: CAMEL-15747 > URL: https://issues.apache.org/jira/browse/CAMEL-15747 > Project: Camel > Issue Type: Improvement > Components: camel-azure >Reporter: Denis Istomin >Assignee: Denis Istomin >Priority: Major > > Currently `regex` property supported by Producer only. > Support of `regex` needs to be implemented on Consumer side. > There is also Disabled integration test that needs to be fixed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (CAMEL-13703) camel-example-cdi-osgi doesn't run in Karaf
[
https://issues.apache.org/jira/browse/CAMEL-13703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Babak Vahdat closed CAMEL-13703.
Resolution: Won't Fix
> camel-example-cdi-osgi doesn't run in Karaf
> ---
>
> Key: CAMEL-13703
> URL: https://issues.apache.org/jira/browse/CAMEL-13703
> Project: Camel
> Issue Type: Task
> Components: examples
>Affects Versions: 3.0.0-M3
>Reporter: Babak Vahdat
>Priority: Major
>
> Following the instructions in \{{README.md}} by this example, using Karaf
> {{4.2.6}} I end up with:
> {code}
> (base) ~/Downloads/apache-karaf-4.2.6/bin>./karaf
> __ __
>/ //_/ __ _/ __/
> / ,< / __ `/ ___/ __ `/ /_
> / /| |/ /_/ / / / /_/ / __/
> /_/ |_|\__,_/_/ \__,_/_/
> Apache Karaf (4.2.6)
> Hit '' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
> karaf@root()> repo-add camel 3.0.0-SNAPSHOT
> Adding feature url
> mvn:org.apache.camel.karaf/apache-camel/3.0.0-SNAPSHOT/xml/features
> karaf@root()> repo-add activemq 5.15.9
> Adding feature url mvn:org.apache.activemq/activemq-karaf/5.15.9/xml/features
> karaf@root()> feature:install activemq-broker-noweb pax-cdi-weld camel-sjms
> camel-cdi
> org.apache.felix.resolver.reason.ReasonException: Unable to resolve root:
> missing requirement [root] osgi.identity; osgi.identity=camel-cdi;
> type=karaf.feature; version="[3.0.0.SNAPSHOT,3.0.0.SNAPSHOT]";
> filter:="(&(osgi.identity=camel-cdi)(type=karaf.feature)(version>=3.0.0.SNAPSHOT)(version<=3.0.0.SNAPSHOT))"
> [caused by: Unable to resolve camel-cdi/3.0.0.SNAPSHOT: missing requirement
> [camel-cdi/3.0.0.SNAPSHOT] osgi.identity;
> osgi.identity=org.apache.camel.camel-cdi; type=osgi.bundle;
> version="[3.0.0.SNAPSHOT,3.0.0.SNAPSHOT]"; resolution:=mandatory [caused by:
> Unable to resolve org.apache.camel.camel-cdi/3.0.0.SNAPSHOT: missing
> requirement [org.apache.camel.camel-cdi/3.0.0.SNAPSHOT] osgi.wiring.package;
> filter:="(&(osgi.wiring.package=javax.enterprise.context)(version>=2.0.0)(!(version>=3.0.0)))"]]
> at
> org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
> at
> org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:392)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:378)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:332)
> at
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:257)
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:393)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1062)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:998)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to
> resolve camel-cdi/3.0.0.SNAPSHOT: missing requirement
> [camel-cdi/3.0.0.SNAPSHOT] osgi.identity;
> osgi.identity=org.apache.camel.camel-cdi; type=osgi.bundle;
> version="[3.0.0.SNAPSHOT,3.0.0.SNAPSHOT]"; resolution:=mandatory [caused by:
> Unable to resolve org.apache.camel.camel-cdi/3.0.0.SNAPSHOT: missing
> requirement [org.apache.camel.camel-cdi/3.0.0.SNAPSHOT] osgi.wiring.package;
> filter:="(&(osgi.wiring.package=javax.enterprise.context)(version>=2.0.0)(!(version>=3.0.0)))"]
> at
> org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
> ... 12 more
> Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to
> resolve org.apache.camel.camel-cdi/3.0.0.SNAPSHOT: missing requirement
> [org.apache.camel.camel-cdi/3.0.0.SNAPSHOT] osgi.wiring.package;
> filter:="(&(osgi.wiring.package=javax.enterprise.context)(version>=2.0.0)(!(version>=3.0.0)))"
> at
> org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
> ... 13 more
> Error executing command: Unable to resolve root: missing requirement [root]
> osgi.identity; osgi.identity=camel-cdi; type=karaf.feature;
> version="[3.0.0.SNAPSHOT,3.0.0.SNAPSHOT]";
> filter:="(&(osgi.identity=camel-cdi)(type=karaf.feature)(version>=3.0.0.SNAPSHOT)(version<=3.0.0.SNAPSHOT))"
> [caused by: Unable to resolve camel-cdi/3.0.0.SNAPSHOT:
[jira] [Commented] (CAMEL-13336) IDE friendly license headers on Java files
[ https://issues.apache.org/jira/browse/CAMEL-13336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16875937#comment-16875937 ] Babak Vahdat commented on CAMEL-13336: -- Thanks for Update, I will try to remove that example in the next days. > IDE friendly license headers on Java files > -- > > Key: CAMEL-13336 > URL: https://issues.apache.org/jira/browse/CAMEL-13336 > Project: Camel > Issue Type: Improvement > Components: build system >Reporter: Zoran Regvart >Assignee: Zoran Regvart >Priority: Major > Fix For: 3.0.0-M2 > > > We can format the Java license headers so that they do not get auto-formatted > by IDEs. > There was a discussion on the dev mailing list about this: > https://mail-archives.apache.org/mod_mbox/camel-dev/201903.mbox/%3C47333568-8d51-8750-b4dc-9a9f2fa00ed3%40gmail.com%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13336) IDE friendly license headers on Java files
[
https://issues.apache.org/jira/browse/CAMEL-13336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16875868#comment-16875868
]
Babak Vahdat commented on CAMEL-13336:
--
[~zregvart] Never mind, I managed to restore and fix that example (BTW the
example was already broken _before_ your commit, sorry :-)).
That said, the example runs now properly using the {{mvn camel:run}} command
but not inside Karaf. For that I created CAMEL-13703
> IDE friendly license headers on Java files
> --
>
> Key: CAMEL-13336
> URL: https://issues.apache.org/jira/browse/CAMEL-13336
> Project: Camel
> Issue Type: Improvement
> Components: build system
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
> Fix For: 3.0.0-M2
>
>
> We can format the Java license headers so that they do not get auto-formatted
> by IDEs.
> There was a discussion on the dev mailing list about this:
> https://mail-archives.apache.org/mod_mbox/camel-dev/201903.mbox/%3C47333568-8d51-8750-b4dc-9a9f2fa00ed3%40gmail.com%3E
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13703) camel-example-cdi-osgi doesn't run in Karaf
Babak Vahdat created CAMEL-13703:
Summary: camel-example-cdi-osgi doesn't run in Karaf
Key: CAMEL-13703
URL: https://issues.apache.org/jira/browse/CAMEL-13703
Project: Camel
Issue Type: Task
Components: examples
Affects Versions: 3.0.0-M3
Reporter: Babak Vahdat
Following the instructions in \{{README.md}} by this example, using Karaf
{{4.2.6}} I end up with:
{code}
(base) ~/Downloads/apache-karaf-4.2.6/bin>./karaf
__ __
/ //_/ __ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.2.6)
Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
karaf@root()> repo-add camel 3.0.0-SNAPSHOT
Adding feature url
mvn:org.apache.camel.karaf/apache-camel/3.0.0-SNAPSHOT/xml/features
karaf@root()> repo-add activemq 5.15.9
Adding feature url mvn:org.apache.activemq/activemq-karaf/5.15.9/xml/features
karaf@root()> feature:install activemq-broker-noweb pax-cdi-weld camel-sjms
camel-cdi
org.apache.felix.resolver.reason.ReasonException: Unable to resolve root:
missing requirement [root] osgi.identity; osgi.identity=camel-cdi;
type=karaf.feature; version="[3.0.0.SNAPSHOT,3.0.0.SNAPSHOT]";
filter:="(&(osgi.identity=camel-cdi)(type=karaf.feature)(version>=3.0.0.SNAPSHOT)(version<=3.0.0.SNAPSHOT))"
[caused by: Unable to resolve camel-cdi/3.0.0.SNAPSHOT: missing requirement
[camel-cdi/3.0.0.SNAPSHOT] osgi.identity;
osgi.identity=org.apache.camel.camel-cdi; type=osgi.bundle;
version="[3.0.0.SNAPSHOT,3.0.0.SNAPSHOT]"; resolution:=mandatory [caused by:
Unable to resolve org.apache.camel.camel-cdi/3.0.0.SNAPSHOT: missing
requirement [org.apache.camel.camel-cdi/3.0.0.SNAPSHOT] osgi.wiring.package;
filter:="(&(osgi.wiring.package=javax.enterprise.context)(version>=2.0.0)(!(version>=3.0.0)))"]]
at
org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
at
org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:392)
at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:378)
at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:332)
at
org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:257)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:393)
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1062)
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:998)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve
camel-cdi/3.0.0.SNAPSHOT: missing requirement [camel-cdi/3.0.0.SNAPSHOT]
osgi.identity; osgi.identity=org.apache.camel.camel-cdi; type=osgi.bundle;
version="[3.0.0.SNAPSHOT,3.0.0.SNAPSHOT]"; resolution:=mandatory [caused by:
Unable to resolve org.apache.camel.camel-cdi/3.0.0.SNAPSHOT: missing
requirement [org.apache.camel.camel-cdi/3.0.0.SNAPSHOT] osgi.wiring.package;
filter:="(&(osgi.wiring.package=javax.enterprise.context)(version>=2.0.0)(!(version>=3.0.0)))"]
at
org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
... 12 more
Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve
org.apache.camel.camel-cdi/3.0.0.SNAPSHOT: missing requirement
[org.apache.camel.camel-cdi/3.0.0.SNAPSHOT] osgi.wiring.package;
filter:="(&(osgi.wiring.package=javax.enterprise.context)(version>=2.0.0)(!(version>=3.0.0)))"
at
org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
... 13 more
Error executing command: Unable to resolve root: missing requirement [root]
osgi.identity; osgi.identity=camel-cdi; type=karaf.feature;
version="[3.0.0.SNAPSHOT,3.0.0.SNAPSHOT]";
filter:="(&(osgi.identity=camel-cdi)(type=karaf.feature)(version>=3.0.0.SNAPSHOT)(version<=3.0.0.SNAPSHOT))"
[caused by: Unable to resolve camel-cdi/3.0.0.SNAPSHOT: missing requirement
[camel-cdi/3.0.0.SNAPSHOT] osgi.identity;
osgi.identity=org.apache.camel.camel-cdi; type=osgi.bundle;
version="[3.0.0.SNAPSHOT,3.0.0.SNAPSHOT]"; resolution:=mandatory [caused by:
Unable to resolve org.apache.camel.camel-cdi/3.0.0.SNAPSHOT: missing
requirement [org.apache.camel.camel-cdi/3.0.0.SNAPSHOT]
[jira] [Commented] (CAMEL-13336) IDE friendly license headers on Java files
[ https://issues.apache.org/jira/browse/CAMEL-13336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16875605#comment-16875605 ] Babak Vahdat commented on CAMEL-13336: -- [~zregvart] the following example looks now strange after this license header update change: https://github.com/apache/camel/tree/master/examples/camel-example-cdi-osgi > IDE friendly license headers on Java files > -- > > Key: CAMEL-13336 > URL: https://issues.apache.org/jira/browse/CAMEL-13336 > Project: Camel > Issue Type: Improvement > Components: build system >Reporter: Zoran Regvart >Assignee: Zoran Regvart >Priority: Major > Fix For: 3.0.0-M2 > > > We can format the Java license headers so that they do not get auto-formatted > by IDEs. > There was a discussion on the dev mailing list about this: > https://mail-archives.apache.org/mod_mbox/camel-dev/201903.mbox/%3C47333568-8d51-8750-b4dc-9a9f2fa00ed3%40gmail.com%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-4921) Code Clean-Up (continued 2)
[
https://issues.apache.org/jira/browse/CAMEL-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Babak Vahdat resolved CAMEL-4921.
-
Resolution: Duplicate
In the meanwhile the {{sandbox/camel-3.x}} branch includes what this ticket
has been raised for, so going to close this one.
> Code Clean-Up (continued 2)
> ---
>
> Key: CAMEL-4921
> URL: https://issues.apache.org/jira/browse/CAMEL-4921
> Project: Camel
> Issue Type: Task
>Reporter: Babak Vahdat
>Assignee: Babak Vahdat
>Priority: Minor
> Fix For: 3.0.0
>
>
> The following tasks are in the scope of this ticket:
> - Usage of the {{@Deprecated}} & {{@Override}} annotations where required
> - Reapply the Clean-ups by CAMEL-4796 and CAMEL-4899 as in the meanwhile this
> is, *again*, required
> - Remove the trailing whitespaces on all lines, even on the empty ones
> - Remove @version from class javadoc
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-11655) Camel-Nagios: Deprecate EncryptionMethod and use Encryption Enum
[ https://issues.apache.org/jira/browse/CAMEL-11655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16136949#comment-16136949 ] Babak Vahdat commented on CAMEL-11655: -- Thanks for fixing. > Camel-Nagios: Deprecate EncryptionMethod and use Encryption Enum > > > Key: CAMEL-11655 > URL: https://issues.apache.org/jira/browse/CAMEL-11655 > Project: Camel > Issue Type: Task > Components: camel-nagios >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino > Fix For: 2.20.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11655) Camel-Nagios: Use Encryption enum instead of EncryptionMethod
[
https://issues.apache.org/jira/browse/CAMEL-11655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16135599#comment-16135599
]
Babak Vahdat commented on CAMEL-11655:
--
{quote}
If this is something critical for you, you can revert commit and do what you
think is best for this component. It was just an attempt to avoid the death of
camel-nagios.
{quote}
[~ancosen] LOL it's not critical for me but for the community :-)
I am not convineced by your answers and kindly ask [~davsclaus] & [~lb] to
share their thoughts about this ticket as well as it's corresponding code
changes. To summurize:
- The made changes are breaking for the upcoming 2.20.0 _minor_ release if a
Camel based application already makes use of the {{encryptionMethod}} query
parameter today in production.
- IMHO Camel should be transparent and not restrict an underlying library API
just because it seems to be buggy or non-working. Bugs _should_ be resolved by
the underlying library itself and not _artificially_ through Camel by
hiding/restricting a given API. See my comments above regarding this point.
- In general, shouldn't we mark a not-recommended-to-be-used Camel API as
deprecated and encourage users to make use of the right/new API. E.g. as it's
done when some {{StringHelper}} new utiliy methods were extracted out of
{{ObjectHelper}} and the corresponding {{ObjectHelper}} methods were marked as
deprecated, see CAMEL-10389. This would make it much much easier both for Camel
code base itself as well as user's code to avoid using the legacy API. I guess
that's exactly what the {{@Deprecated}} annotation good for. I don't seem to
understand what it would be wrong with such an approach, that's, marking
{{encryptionMethod}} query parameter as deprecaterd and encourage useres to
make use of the new {{encryption}} query parameter and then support both of
them. Supporting both would not break a pre-existing application on the
production and then we could find and remove the deprecated API by Camel 3 much
easier.
WDYT?
> Camel-Nagios: Use Encryption enum instead of EncryptionMethod
> -
>
> Key: CAMEL-11655
> URL: https://issues.apache.org/jira/browse/CAMEL-11655
> Project: Camel
> Issue Type: Task
> Components: camel-nagios
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
> Fix For: 2.20.0
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CAMEL-11655) Camel-Nagios: Use Encryption enum instead of EncryptionMethod
[
https://issues.apache.org/jira/browse/CAMEL-11655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134817#comment-16134817
]
Babak Vahdat commented on CAMEL-11655:
--
[~ancosen] Thanks for your feedback.
Could you please point to the bug report or ticket you're talking about so the
real rationale behind this jira ticket becomes clear to others. I guess it's
about this enum:
https://github.com/jsendnsca/jsendnsca/blob/master/src/main/java/com/googlecode/jsendnsca/encryption/Encryption.java
IMHO we should not restrict the API only to those three enum members NONE, XOR
and Triple_Des just because the others don't work. If that's really the case it
should be resolved on the jsendnsca side and we _should not_ restrict the API
to only those 3 members just because the others don't work. IMHO Camel should
be transparent about this. What if the Blowfish encryption gets fixed by the
next jsendnsca release and we update to that version in Camel? Are we going to
suddenly allow that Blowfish encryption as well and add another {{else if}} for
that?
And what do you think about marking {{NagiosEncryptionMethod}} enum as
deprecated? Does it make sense?
> Camel-Nagios: Use Encryption enum instead of EncryptionMethod
> -
>
> Key: CAMEL-11655
> URL: https://issues.apache.org/jira/browse/CAMEL-11655
> Project: Camel
> Issue Type: Task
> Components: camel-nagios
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
> Fix For: 2.20.0
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CAMEL-11655) Camel-Nagios: Use Encryption enum instead of EncryptionMethod
[
https://issues.apache.org/jira/browse/CAMEL-11655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16133400#comment-16133400
]
Babak Vahdat commented on CAMEL-11655:
--
[~ancosen] IMHO this's a breaking change for the upcoming {{2.20.0}} version as
the {{encryptionMethod}} query parameter has been simply removed and replaced
with a new {{encryption}} query parameter, which _would_ break user's code
making use of this option. AFAIK a minor release should not include any
breaking changes, right? Shouldn't we better somehow mark {{encryptionMethod}}
as deprecated and encourage users to make use of the new {{encryption}}
parameter instead? Other than that some feedback on your made code changes:
What would be wrong to do:
{code}
nagiosSettings.setEncryption(encryption);
{code}
Instead of the following if / else if:
{code}
if (encryption != null) {
if (Encryption.NONE == encryption) {
nagiosSettings.setEncryption(Encryption.NONE);
} else if (Encryption.XOR == encryption) {
nagiosSettings.setEncryption(Encryption.XOR);
} else if (Encryption.TRIPLE_DES == encryption) {
nagiosSettings.setEncryption(Encryption.TRIPLE_DES);
} else {
throw new IllegalArgumentException("Unknown encryption method: " +
encryption);
}
}
{code}
As because:
{code}
private Encryption encryption = Encryption.NONE;
{code}
Also maybe mark the {{NagiosEncryptionMethod}} enum itself as deprecated so we
don't forget to remove it in Camel 3.
> Camel-Nagios: Use Encryption enum instead of EncryptionMethod
> -
>
> Key: CAMEL-11655
> URL: https://issues.apache.org/jira/browse/CAMEL-11655
> Project: Camel
> Issue Type: Task
> Components: camel-nagios
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
> Fix For: 2.20.0
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (CAMEL-11638) Upgrade to Apache SSHD 1.6.x
[
https://issues.apache.org/jira/browse/CAMEL-11638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Babak Vahdat resolved CAMEL-11638.
--
Resolution: Fixed
> Upgrade to Apache SSHD 1.6.x
>
>
> Key: CAMEL-11638
> URL: https://issues.apache.org/jira/browse/CAMEL-11638
> Project: Camel
> Issue Type: Task
> Components: camel-ssh
>Reporter: Babak Vahdat
>Assignee: Babak Vahdat
>Priority: Minor
> Fix For: 2.20.0
>
>
> Currently on the master branch we make use of Apache SSHD version {{0.14.0}}
> which is apparently not binary compatible with {{1.6.x}}, so that it needs a
> bit of code adjustment to compile and make the tests run green. Probably the
> corresponding Karaf feature needs some changes as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (CAMEL-11638) Upgrade to Apache SSHD 1.6.x
[
https://issues.apache.org/jira/browse/CAMEL-11638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Babak Vahdat updated CAMEL-11638:
-
Fix Version/s: (was: 2.19.3)
2.20.0
> Upgrade to Apache SSHD 1.6.x
>
>
> Key: CAMEL-11638
> URL: https://issues.apache.org/jira/browse/CAMEL-11638
> Project: Camel
> Issue Type: Task
> Components: camel-ssh
>Reporter: Babak Vahdat
>Assignee: Babak Vahdat
>Priority: Minor
> Fix For: 2.20.0
>
>
> Currently on the master branch we make use of Apache SSHD version {{0.14.0}}
> which is apparently not binary compatible with {{1.6.x}}, so that it needs a
> bit of code adjustment to compile and make the tests run green. Probably the
> corresponding Karaf feature needs some changes as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (CAMEL-11638) Upgrade to Apache SSHD 1.6.x
[
https://issues.apache.org/jira/browse/CAMEL-11638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Babak Vahdat updated CAMEL-11638:
-
Description: Currently on the master branch we make use of Apache SSHD
version {{0.14.0}} which is apparently not binary compatible with {{1.6.x}}, so
that it needs a bit of code adjustment to compile and make the tests run green.
Probably the corresponding Karaf feature needs some changes as well. (was:
Currently on the master branch we make use of Apache SSHD version {{0.14.0}}
which is apparently not binary compatible with {{1.6.x}}, so that it needs a
bit of code adjustment to compile and make the tests run green. Probably the
corresponding Karaf future needs some changes as well. )
> Upgrade to Apache SSHD 1.6.x
>
>
> Key: CAMEL-11638
> URL: https://issues.apache.org/jira/browse/CAMEL-11638
> Project: Camel
> Issue Type: Task
> Components: camel-ssh
>Reporter: Babak Vahdat
>Assignee: Babak Vahdat
>Priority: Minor
> Fix For: 2.19.3
>
>
> Currently on the master branch we make use of Apache SSHD version {{0.14.0}}
> which is apparently not binary compatible with {{1.6.x}}, so that it needs a
> bit of code adjustment to compile and make the tests run green. Probably the
> corresponding Karaf feature needs some changes as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (CAMEL-11638) Upgrade to Apache SSHD 1.6.x
Babak Vahdat created CAMEL-11638:
Summary: Upgrade to Apache SSHD 1.6.x
Key: CAMEL-11638
URL: https://issues.apache.org/jira/browse/CAMEL-11638
Project: Camel
Issue Type: Task
Components: camel-ssh
Reporter: Babak Vahdat
Assignee: Babak Vahdat
Priority: Minor
Fix For: 2.19.3
Currently on the master branch we make use of Apache SSHD version {{0.14.0}}
which is apparently not binary compatible with {{1.6.x}}, so that it needs a
bit of code adjustment to compile and make the tests run green. Probably the
corresponding Karaf future needs some changes as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (CAMEL-10544) Upgrade to smack 4.2.0
[ https://issues.apache.org/jira/browse/CAMEL-10544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat resolved CAMEL-10544. -- Resolution: Fixed > Upgrade to smack 4.2.0 > -- > > Key: CAMEL-10544 > URL: https://issues.apache.org/jira/browse/CAMEL-10544 > Project: Camel > Issue Type: Improvement > Components: camel-xmpp >Affects Versions: 2.19.0 >Reporter: Christian Schneider >Assignee: Babak Vahdat >Priority: Minor > Fix For: 2.20.0 > > > Smack 4.2 changed some of the API. This issue covers upgrading the dependency > as well as the camel-xmpp code. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (CAMEL-10544) Upgrade to smack 4.2.0
[ https://issues.apache.org/jira/browse/CAMEL-10544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat reassigned CAMEL-10544: Assignee: Babak Vahdat (was: Christian Schneider) Affects Version/s: (was: 2.18.0) 2.19.0 Priority: Minor (was: Major) Fix Version/s: (was: Future) 2.20.0 Description: Smack 4.2 changed some of the API. This issue covers upgrading the dependency as well as the camel-xmpp code. (was: Smack 4.1 changed some of the API. This issue covers upgrading the dependency as well as the camel-xmpp code.) Summary: Upgrade to smack 4.2.0 (was: Upgrade to smack 4.1) > Upgrade to smack 4.2.0 > -- > > Key: CAMEL-10544 > URL: https://issues.apache.org/jira/browse/CAMEL-10544 > Project: Camel > Issue Type: Improvement > Components: camel-xmpp >Affects Versions: 2.19.0 >Reporter: Christian Schneider >Assignee: Babak Vahdat >Priority: Minor > Fix For: 2.20.0 > > > Smack 4.2 changed some of the API. This issue covers upgrading the dependency > as well as the camel-xmpp code. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-10544) Upgrade to smack 4.1
[ https://issues.apache.org/jira/browse/CAMEL-10544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014676#comment-16014676 ] Babak Vahdat commented on CAMEL-10544: -- As there's been no progress on this ticket I've looked into it and have got a patch in place. So I'm taking the liberty of assigning this to myself. And in the meanwhile smack version 4.2.0 is already out. So going to adapt the description of this ticket as well. > Upgrade to smack 4.1 > > > Key: CAMEL-10544 > URL: https://issues.apache.org/jira/browse/CAMEL-10544 > Project: Camel > Issue Type: Improvement > Components: camel-xmpp >Affects Versions: 2.18.0 >Reporter: Christian Schneider >Assignee: Christian Schneider > Fix For: Future > > > Smack 4.1 changed some of the API. This issue covers upgrading the dependency > as well as the camel-xmpp code. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CAMEL-8852) Camel JCR doesnt include Connection to a repository workspace except the default one
[ https://issues.apache.org/jira/browse/CAMEL-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat updated CAMEL-8852: Affects Version/s: 2.15.2 Fix Version/s: (was: Future) 2.16.0 Camel JCR doesnt include Connection to a repository workspace except the default one Key: CAMEL-8852 URL: https://issues.apache.org/jira/browse/CAMEL-8852 Project: Camel Issue Type: Improvement Components: camel-jcr Affects Versions: 2.15.2 Reporter: Tarek CHAOUALI Assignee: Andrea Cosentino Fix For: 2.16.0 This bug exists in all camel jcr component version Camel JCR component provides a connection to the default workspace no custom workspace connection is allowed . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8750) Camel-Infinispan: Add Remove, RemoveAsync, Replace, ReplaceAsync operation for a specific value
[ https://issues.apache.org/jira/browse/CAMEL-8750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat updated CAMEL-8750: Affects Version/s: 2.15.2 Fix Version/s: 2.16.0 Camel-Infinispan: Add Remove, RemoveAsync, Replace, ReplaceAsync operation for a specific value --- Key: CAMEL-8750 URL: https://issues.apache.org/jira/browse/CAMEL-8750 Project: Camel Issue Type: Improvement Components: camel-infinispan Affects Versions: 2.15.2 Reporter: Andrea Cosentino Assignee: Andrea Cosentino Priority: Minor Fix For: 2.16.0 Actually the infinispan component doesn't expose the following methods: replace(K key, V oldValue, V value, long lifespan, TimeUnit lifespanUnit, long maxIdleTime, TimeUnit maxIdleTimeUnit) replace(K key, V oldValue, V value, long lifespan, TimeUnit unit) removeAsync(Object key, Object value) remove(Object key, Object value) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8706) Increase set of parameters for elasticsearch component
[ https://issues.apache.org/jira/browse/CAMEL-8706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat updated CAMEL-8706: Fix Version/s: 2.16.0 Increase set of parameters for elasticsearch component -- Key: CAMEL-8706 URL: https://issues.apache.org/jira/browse/CAMEL-8706 Project: Camel Issue Type: Improvement Components: camel-elasticsearch Affects Versions: 2.15.1 Reporter: Mauricio Jost Assignee: Andrea Cosentino Priority: Minor Fix For: 2.16.0 The elasticsearch component does not allow to set a multi-transport-addresses client as endpoint, even though the underlying elasticsearch client supports it. It does not allow either to choose any of replication type, or write consistency level for INDEX operations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8813) Correct/update camel-hazelcast documentation
[ https://issues.apache.org/jira/browse/CAMEL-8813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat updated CAMEL-8813: Affects Version/s: 2.15.2 Fix Version/s: 2.16.0 Correct/update camel-hazelcast documentation Key: CAMEL-8813 URL: https://issues.apache.org/jira/browse/CAMEL-8813 Project: Camel Issue Type: Task Components: documentation Affects Versions: 2.15.2 Reporter: Tomas Rohovsky Assignee: Andrea Cosentino Fix For: 2.16.0 * Usage of Multi Map section is present two times *# the first should be removed as it contains description for unsupported operations (update, query) and miss description for removevalue. * Add newly added operations to map producer (PUT_IF_ABSENT_OPERATION, GET_ALL_OPERATION, CLEAR_OPERATION) * Add newly added operation to multimap producer (CLEAR_OPERATION) * Change to(hazelcast:atomicnumber:foo) to to(hazelcast:atomicvalue:foo) *# IMO atomicnumber is actually a better name for this endpoint, but changing it would break backward compatibility * Mention that OBJECT_POS header is used for indexing in list producer * Remove non-actual comments like Please note that set,get and removevalue and not yet supported by hazelcast, will be added in the future.. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8093) Adding Message headers for sinceid, maxid, user
[ https://issues.apache.org/jira/browse/CAMEL-8093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat updated CAMEL-8093: Affects Version/s: 2.15.2 Fix Version/s: 2.16.0 Adding Message headers for sinceid, maxid, user --- Key: CAMEL-8093 URL: https://issues.apache.org/jira/browse/CAMEL-8093 Project: Camel Issue Type: New Feature Components: camel-twitter Affects Versions: 2.15.2 Reporter: Matteo Redaelli Assignee: Andrea Cosentino Priority: Minor Fix For: 2.16.0 Useful for creating dynamic twitter services and for retreiving quickly many old tweets (timelines and searches) iterating several times the twitter APIs... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8695) Update apns library to 1.0.0.Beta6
[ https://issues.apache.org/jira/browse/CAMEL-8695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat updated CAMEL-8695: Fix Version/s: 2.16.0 Update apns library to 1.0.0.Beta6 -- Key: CAMEL-8695 URL: https://issues.apache.org/jira/browse/CAMEL-8695 Project: Camel Issue Type: Improvement Components: camel-apns Affects Versions: 2.13.3 Reporter: Justin Heesemann Assignee: Andrea Cosentino Fix For: 2.16.0 Current version of java-apns in apache-camel is 0.2.3. From it's website: There currently is a perelease for 1.0.0 which fixes a number of problems over 0.2.3. There's still a CI test that sporadically fails on Travis-CI only, but not on other test machines I have access to. Supposedly it is a still undetected race condition. However 1.0.0 Beta fixes a lot of problems over 0.2.x, so even as it is called beta I'd recommend to use the beta instead of the 0.2.3 even for production. I tried to use Beta6 in camel-apns-2.13.3 and it seemed to work fine, without code changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8729) Add query all capabilities in hazelcast map producers
[
https://issues.apache.org/jira/browse/CAMEL-8729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14523948#comment-14523948
]
Babak Vahdat commented on CAMEL-8729:
-
[~ancosen] {{ObjectHelper.isNotEmpty(foo)}} checks for {{null}} as well so that
an extra {{foo != null}} condition check is obsolete / not required. There’re
also similar logic being added for camel-openshift recently, like
[here|https://github.com/apache/camel/blob/master/components/camel-openshift/src/main/java/org/apache/camel/component/openshift/OpenShiftProducer.java#L432].
Also I guess we can remove the Fix version of 2.15.2 for this ticket as it’s
not a bug which we need to back port, right?
BTW thanks for all your contributions and welcome aboard :)
Add query all capabilities in hazelcast map producers
-
Key: CAMEL-8729
URL: https://issues.apache.org/jira/browse/CAMEL-8729
Project: Camel
Issue Type: Improvement
Components: camel-hazelcast
Affects Versions: 2.15.1
Reporter: Juan Jose Vazquez Delgado
Assignee: Andrea Cosentino
Fix For: 2.15.2, 2.16.0
Currently, it's not possible to get all map entries. In the current
implementation, get operation requires some key specified. Also, query
operation requires a non-empty sql predicate.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-7877) json DataFormat: provide the prettyPrint option by all the supported JSON libraries
[
https://issues.apache.org/jira/browse/CAMEL-7877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Babak Vahdat updated CAMEL-7877:
Description:
See:
http://camel.465427.n5.nabble.com/Problems-prettyPrinting-JSON-after-camel-2-14-0-upgrade-td5756738.html
It would be nice to have support for the {{prettyPrint}} option no matter if
the XStream, Jackson or GSon library is in use.
was:
See:
http://camel.465427.n5.nabble.com/Problems-prettyPrinting-JSON-after-camel-2-14-0-upgrade-td5756738.html
It would be nice to have support for the {{prettyPrint}} option no matter if
the XStream, Jettsion, Jackson or GSon library is in use.
json DataFormat: provide the prettyPrint option by all the supported JSON
libraries
---
Key: CAMEL-7877
URL: https://issues.apache.org/jira/browse/CAMEL-7877
Project: Camel
Issue Type: New Feature
Reporter: Babak Vahdat
Assignee: Babak Vahdat
Priority: Minor
Fix For: 2.16.0
See:
http://camel.465427.n5.nabble.com/Problems-prettyPrinting-JSON-after-camel-2-14-0-upgrade-td5756738.html
It would be nice to have support for the {{prettyPrint}} option no matter if
the XStream, Jackson or GSon library is in use.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CAMEL-7877) json DataFormat: provide the prettyPrint option by all the supported JSON libraries
[
https://issues.apache.org/jira/browse/CAMEL-7877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Babak Vahdat reassigned CAMEL-7877:
---
Assignee: Babak Vahdat
json DataFormat: provide the prettyPrint option by all the supported JSON
libraries
---
Key: CAMEL-7877
URL: https://issues.apache.org/jira/browse/CAMEL-7877
Project: Camel
Issue Type: New Feature
Reporter: Babak Vahdat
Assignee: Babak Vahdat
Priority: Minor
Fix For: 2.16.0
See:
http://camel.465427.n5.nabble.com/Problems-prettyPrinting-JSON-after-camel-2-14-0-upgrade-td5756738.html
It would be nice to have support for the {{prettyPrint}} option no matter if
the XStream, Jettsion, Jackson or GSon library is in use.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-7877) json DataFormat: support the prettyPrint option by all the supported JSON libraries
[
https://issues.apache.org/jira/browse/CAMEL-7877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Babak Vahdat updated CAMEL-7877:
Summary: json DataFormat: support the prettyPrint option by all the
supported JSON libraries (was: json DataFormat: provide the prettyPrint option
by all the supported JSON libraries)
json DataFormat: support the prettyPrint option by all the supported JSON
libraries
---
Key: CAMEL-7877
URL: https://issues.apache.org/jira/browse/CAMEL-7877
Project: Camel
Issue Type: New Feature
Reporter: Babak Vahdat
Assignee: Babak Vahdat
Priority: Minor
Fix For: 2.16.0
See:
http://camel.465427.n5.nabble.com/Problems-prettyPrinting-JSON-after-camel-2-14-0-upgrade-td5756738.html
It would be nice to have support for the {{prettyPrint}} option no matter if
the XStream, Jackson or GSon library is in use.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CAMEL-8160) Generic methods used as endpoints fail in Java 8
[ https://issues.apache.org/jira/browse/CAMEL-8160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat reassigned CAMEL-8160: --- Assignee: Babak Vahdat Generic methods used as endpoints fail in Java 8 Key: CAMEL-8160 URL: https://issues.apache.org/jira/browse/CAMEL-8160 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.14.0, 2.14.1 Environment: mac, java 8 Reporter: Andrew Celerity Assignee: Babak Vahdat Attachments: cameljava8.zip In Java 8 annotations are duplicated to generics' bridge methods. Camel, rightly, does not support bridge methods as endpoints. However, because of this change in the language annotations such as @Consume will end up on them after compilation leaving Camel in an invalid state. I will attach a sample project. This ticket is from this discussion thread: http://camel.465427.n5.nabble.com/Changes-in-Java-8-generics-breaking-Camel-td5760638.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8160) Generic methods used as endpoints fail in Java 8
[ https://issues.apache.org/jira/browse/CAMEL-8160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat updated CAMEL-8160: Affects Version/s: (was: 2.14.1) Fix Version/s: 2.15.0 2.14.2 Generic methods used as endpoints fail in Java 8 Key: CAMEL-8160 URL: https://issues.apache.org/jira/browse/CAMEL-8160 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.14.0 Environment: mac, java 8 Reporter: Andrew Celerity Assignee: Babak Vahdat Fix For: 2.14.2, 2.15.0 Attachments: cameljava8.zip In Java 8 annotations are duplicated to generics' bridge methods. Camel, rightly, does not support bridge methods as endpoints. However, because of this change in the language annotations such as @Consume will end up on them after compilation leaving Camel in an invalid state. I will attach a sample project. This ticket is from this discussion thread: http://camel.465427.n5.nabble.com/Changes-in-Java-8-generics-breaking-Camel-td5760638.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-4921) Code Clean-Up (continued 2)
[
https://issues.apache.org/jira/browse/CAMEL-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14231319#comment-14231319
]
Babak Vahdat commented on CAMEL-4921:
-
Some further work on this ticket:
https://github.com/apache/camel/commit/c8ae4cac990afd79704d318de8fbecea8f684a0d
https://github.com/apache/camel/commit/c7f775ffc179e7c87efc1d41d05116e1c1813659
https://github.com/apache/camel/commit/0e195428ee04531be27a0b659005e3aa8d159d23
https://github.com/apache/camel/commit/cc5c00f54365fda65cfb823ba984ce2b1af5bce5
https://github.com/apache/camel/commit/c778bbcd680ce0b405e2cefb8e0d3b0c20a1efd3
Code Clean-Up (continued 2)
---
Key: CAMEL-4921
URL: https://issues.apache.org/jira/browse/CAMEL-4921
Project: Camel
Issue Type: Task
Reporter: Babak Vahdat
Assignee: Babak Vahdat
Priority: Minor
Fix For: 3.0.0
The following tasks are in the scope of this ticket:
- Usage of the {{@Deprecated}} {{@Override}} annotations where required
- Reapply the Clean-ups by CAMEL-4796 and CAMEL-4899 as in the meanwhile this
is, *again*, required
- Remove the trailing whitespaces on all lines, even on the empty ones
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (CAMEL-4921) Code Clean-Up (continued 2)
[
https://issues.apache.org/jira/browse/CAMEL-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14231319#comment-14231319
]
Babak Vahdat edited comment on CAMEL-4921 at 12/2/14 2:09 PM:
--
Some further work for this ticket:
https://github.com/apache/camel/commit/c8ae4cac990afd79704d318de8fbecea8f684a0d
https://github.com/apache/camel/commit/c7f775ffc179e7c87efc1d41d05116e1c1813659
https://github.com/apache/camel/commit/0e195428ee04531be27a0b659005e3aa8d159d23
https://github.com/apache/camel/commit/cc5c00f54365fda65cfb823ba984ce2b1af5bce5
https://github.com/apache/camel/commit/c778bbcd680ce0b405e2cefb8e0d3b0c20a1efd3
https://github.com/apache/camel/commit/da1813bbf36080c5ed976fc5f6a1665ed067ff75
was (Author: bvahdat):
Some further work on this ticket:
https://github.com/apache/camel/commit/c8ae4cac990afd79704d318de8fbecea8f684a0d
https://github.com/apache/camel/commit/c7f775ffc179e7c87efc1d41d05116e1c1813659
https://github.com/apache/camel/commit/0e195428ee04531be27a0b659005e3aa8d159d23
https://github.com/apache/camel/commit/cc5c00f54365fda65cfb823ba984ce2b1af5bce5
https://github.com/apache/camel/commit/c778bbcd680ce0b405e2cefb8e0d3b0c20a1efd3
Code Clean-Up (continued 2)
---
Key: CAMEL-4921
URL: https://issues.apache.org/jira/browse/CAMEL-4921
Project: Camel
Issue Type: Task
Reporter: Babak Vahdat
Assignee: Babak Vahdat
Priority: Minor
Fix For: 3.0.0
The following tasks are in the scope of this ticket:
- Usage of the {{@Deprecated}} {{@Override}} annotations where required
- Reapply the Clean-ups by CAMEL-4796 and CAMEL-4899 as in the meanwhile this
is, *again*, required
- Remove the trailing whitespaces on all lines, even on the empty ones
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-8111) Upgrade to Pax Exam 4.3
Babak Vahdat created CAMEL-8111: --- Summary: Upgrade to Pax Exam 4.3 Key: CAMEL-8111 URL: https://issues.apache.org/jira/browse/CAMEL-8111 Project: Camel Issue Type: Task Components: osgi, tests Reporter: Babak Vahdat Assignee: Babak Vahdat Priority: Minor Fix For: 2.15.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8111) Upgrade to Pax Exam 4.3
[
https://issues.apache.org/jira/browse/CAMEL-8111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Babak Vahdat resolved CAMEL-8111.
-
Resolution: Fixed
Verified the upgrade both with/without the profile {{karaf3}}.
Upgrade to Pax Exam 4.3
---
Key: CAMEL-8111
URL: https://issues.apache.org/jira/browse/CAMEL-8111
Project: Camel
Issue Type: Task
Components: osgi, tests
Reporter: Babak Vahdat
Assignee: Babak Vahdat
Priority: Minor
Fix For: 2.15.0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
