@fyodor,
if you are familiar with camel-jbang
Try this:
Here is updated form
https://gist.github.com/chiragsanghavi/02a00f49ac7ee9a978344af571746c02
Yaml DSL:
https://gist.github.com/chiragsanghavi/8a2aee132fc626ed25f97fc0a360ead4
Try form 1 (to see the issue) and try form 2 to see it work as
Can you try and run it with undertow? I see test similar to your
scenario in undertow.
https://github.com/apache/camel/tree/52443a298935b2842a402cb5fff7e37abb938f8b/components/camel-undertow/src/test/java/org/apache/camel/component/undertow
ચિરાગ/चिराग/Chirag
The old-fashioned standard of the Servlet API required that the request
parameters were available through the request.getParameter* methods,
including the getParameterMap(), be that GET query parameters or the
POST form data load.
Camel collects anything looking like a Map into the Camel
Thank you Claus.
I recently found out, why we didn't use the following code:
CxfEndpoint endpoint = (CxfEndpoint)
camelContext.getEndpoint("cxf://http://remotehost/ws/service;);
It happens that one of the soap service urls has query string like in the
following example:
CxfEndpoint
if you introspect variables, the fields are not populated in
HttpServletRequest object. The variables are added to the Camel
Exchange Header. This may be something done within camel-jetty or one
of the underlying libraries.
the field are populated in the message header - but at that point,
they
Hi
See this FAQ
https://camel.apache.org/manual/faq/how-to-create-executable-jar-camel-main.html#_using_maven_shade_plugin
On Wed, Jun 14, 2023 at 5:10 PM Sujeet Singh
wrote:
> Hi,
>
> The issue is resolved now.
>
> We loaded the context like below
>
> AbstractApplicationContext context = new
Hi,
The issue is resolved now.
We loaded the context like below
AbstractApplicationContext context = new
ClassPathXmlApplicationContext(contextConfigxml);
context.start();
context.registerShutdownHook();|
The major factor though was we used below as one of the transformer in
maven shade
Thanks all folks.
I forgot to send an email and close this voting as passed.
Cheers,
Pasquale.
On Wed, Jun 7, 2023 at 2:56 PM Pasquale Congiusti <
pasquale.congiu...@gmail.com> wrote:
> Hello,
>
> This is a combined vote to release Apache Camel K 1.12.1 and Camel K
> Runtime1.17.1. The release
Hi,
Great to hear, thank you!
On Tuesday, June 13, 2023, Claus Ibsen wrote:
> Hi
>
> Okay so your use-cases will then work out of the box in 3.20.6 onwards.
>
> On Tue, Jun 13, 2023 at 2:59 PM Claus Ibsen wrote:
>
> > Hi
> >
> > I tracked down what I consider a little bug
> >
Hi,
+1 (binding)
Thank you Pasquale,
Regards,
Nicolas
From: Pasquale Congiusti
Sent: Wednesday, June 7, 2023 14:56
To: dev ; users@camel.apache.org
Subject: [VOTE] Release Apache Camel K 1.12.1 and Camel K runtime 1.17.1 -
second attempt
Hello,
This is a
+1 (binding)
Thanks Pasquale!
--
Babak
> On 7 Jun 2023, at 14:56, Pasquale Congiusti
> wrote:
>
> Hello,
>
> This is a combined vote to release Apache Camel K 1.12.1 and Camel K
> Runtime1.17.1. The release also contains the Camel K CRD 1.12.1, a Java
> client for Kubernetes Camel K CRDs.
Hi Chirag, yeah that exactly is the question - it shouldn't be that way.
If we change Camel version in the pom.xml to Camel 2.24, it'll work as
expected: the POST payload will be parsed into java.util.Map and the
Json will be generated (instead of "null").
So the question is -- how do i fix
12 matches
Mail list logo
