Camel 3.7.x doesn't support Karaf 4.3.0, the last version we tested is 4.2.9
Il giorno mar 26 gen 2021 alle ore 22:00 Schulze, Jan <
jan.schu...@uni-tuebingen.de> ha scritto:
> Hi Claus,
>
>
> thanks for your reply. I forgot to mention, that I am using Camel in Karaf.
>
> Along with Camel I also
Hi Claus,
thanks for your reply. I forgot to mention, that I am using Camel in Karaf.
Along with Camel I also upgraded Karaf (4.2.9 => 4.3.0).
When using Camel 2.7.1 with Karaf 4.2.9, the camel-ssh component is working
without problems.
Also, the camel features URLs for installing Camel
Hi all,
I’ve a Question About the usage of Route templates (Camel-3.7.0).
As far as I see, it is possible to provide every kind of object as a paramter.
But within the template, it seems to me, that those Parameters are
only processed as Strings.
So my question:
Is there a way/best practice to
Seems like a bug
Here is a full dependencyManagement and dependencies parts of pom.xml made
according to https://camel.apache.org/camel-spring-boot/latest/index.html
org.apache.camel.springboot
camel-spring-boot-bom
${camel-version}
pom
I suggest publishing this work around in camel-examples (
https://github.com/apache/camel-examples/pull/32). If you have any comments
to my MR, you are welcome.
On Tue, 26 Jan 2021 at 19:53, Omar Al-Safi wrote:
> Glad to hear that!
>
> However, if you have an idea how to handle these listBlobs,
Glad to hear that!
However, if you have an idea how to handle these listBlobs, please feel
free to send a PR with your proposed fix.
Regards,
Omar
On Tue, Jan 26, 2021 at 2:14 PM Mark Andreev wrote:
> I found a solution for this issue. When I use Azure Api directly and
> operate with Page all
I figured out it is related to having camelContext described in camel.xml along
with another beans and for example camel-activemq-starter dependency in pom.xml
The one way to eliminate camelContext reloading is to drop camelContext
description at all, xml routes then could be placed in
I found a solution for this issue. When I use Azure Api directly and
operate with Page all works. It is useful when your azure blob storage
contains a lot of blobs (in my case ~250k).
from("direct:list")
.routeId("listBlobs")
.process(exchange -> {
BlobServiceClient
Hi
Thanks for reporting. Can you create a JIRA ticket.
And would you be able to try test with switching to use mina 2.0 JAR
on the classpath but keep using the 3.7.1 camel version.
On Tue, Jan 26, 2021 at 1:20 PM Schulze, Jan
wrote:
>
> Hi,
>
> "camel-ssh" component is throwing a
Hi,
"camel-ssh" component is throwing a CamelExecutionException when it is used to
write a file via SSH.
It used to be working in Camel 3.4.0, but after upgrading to 3.7.1, I observe
the following stack trace:
org.apache.camel.CamelExecutionException: Exception occurred during execution
on
Hi,
Actually you are doing nothing wrong here. Apparently when you set
maxResultsPerPage, in Azure client, that means it will return pageable
list, now in every pagelist it will return the max blobs that you set
earlier in `maxResultsPerPage` which is IMO pretty weird from Azure's side.
Now in
11 matches
Mail list logo
