This works! Thank you very much Nicola!
Regards,
Mark
On Mon, 11 Jan 2021 at 17:04, Nicola Ferraro wrote:
> Hi,
> since 1.2 Camel K has moved into using Quarkus as runtime (in 1.3 the old
> runtime based on main has been removed). So now it's recommended to use the
> Quarkus internal http serve
Hi,
since 1.2 Camel K has moved into using Quarkus as runtime (in 1.3 the old
runtime based on main has been removed). So now it's recommended to use the
Quarkus internal http server for exposing HTTP functions instead of Jetty.
In order to use it, you can try consuming:
from("platform-http:/hell
Hello,
I have a simple Jetty Integration which worked well mid-last year, but that
will not compile with kamel 1.2.1 or 1.3. I'm running on OpenShift 4.6.
Here's the source code:
import org.apache.camel.builder.RouteBuilder;
public class Jetty extends RouteBuilder {
@Override
public void conf
Hello,
I have a simple Jetty Integration which worked well mid-last year, but that
will not compile with kamel 1.2.1 or 1.3. I'm running on OpenShift 4.6.
Here's the source code:
import org.apache.camel.builder.RouteBuilder;
public class Jetty extends RouteBuilder {
@Override
public void conf
Thank you "ski n" for the cheat sheet. It looks great.
On Mon, Jan 11, 2021 at 6:15 AM ski n wrote:
> Hi All,
>
> For a project I created a lot of Camel routes. Sometimes I noticed that I
> need to look up how to do something. To look it up more quickly I created a
> cheat sheet for the Java DSL
Hi All,
For a project I created a lot of Camel routes. Sometimes I noticed that I
need to look up how to do something. To look it up more quickly I created a
cheat sheet for the Java DSL.
Maybe also useful for others:
https://github.com/assimbly/camel-examples
In case you miss something just ma
Hi Zheng:
We are using Netty for TCP socket connections, not for http.
Thanks
Ravi
-Original Message-
From: Zheng Feng
Sent: Monday, January 11, 2021 9:06 AM
To: users@camel.apache.org
Subject: Re: Camel-Netty Security Vulnerability (CWE-295/BDSA-2018-4022) -
Hostname verification
It
It looks like we had resolved the similar issue in
https://issues.apache.org/jira/browse/CAMEL-14070 to support SNI. So IMO,
the camel-netty-http will not be affected by this vulnerability.
On Mon, Jan 11, 2021 at 9:43 PM Ravi Sunchu
wrote:
> Hi All:
>
> In a project where we are using camel-net
Hi Andrea:
We are using Camel 3.4.4.
My apologies for posting to the wrong mailing list. Admins, please delete this
post from this mailing list. I will report this to ASF security team.
Given that this was a vulnerability that was identified 2 years ago, I thought
I was missing something and t
Please report the camel version you're using.
I think this shouldn't be discussed at users ml, but you should contact ASF
security mail address.
Il lun 11 gen 2021, 14:35 Ravi Sunchu ha
scritto:
> Hi All:
>
> In a project where we are using camel-netty component, our Blackduck scans
> reporte
Hi All:
In a project where we are using camel-netty component, our Blackduck scans
reported a medium (4.7) security vulnerability against netty-4.1.53.Final
version. The essence of the vulnerability seems to be that Netty client does
not verify the hostname of the server against the certificate
Hi
Just give it a try on 2.x.
On Mon, Jan 11, 2021 at 1:39 PM Mantas Gridinas wrote:
>
> Yo!
>
> I would like toD EIP to throw when it would create an endpoint, rather
> than create it. I've been reading a bit about toD EIP (for 3.x, since
> 2.x documentation is not available for it anymore?) a
Yo!
I would like toD EIP to throw when it would create an endpoint, rather
than create it. I've been reading a bit about toD EIP (for 3.x, since
2.x documentation is not available for it anymore?) and I found the
following flag:
ignoreInvalidEndpoint - Ignore the invalidate endpoint exception whe
13 matches
Mail list logo
