Hi all,
I'm using the latest camel (3.9.0) and I'm encountering an
AmbiguousMethodCallException when using POJO producing. I use the
@Produce annotation and turn off binding. This setup works in camel
2.21.5. I was comparing camel 3.9.0 and camel 2.21.5 and noticed in
the
Thnx Clause.
So 3.7.0 gives an error and 3.8.0+ will "fix" this silently. Does this mean it
automatically creates a sub route for it or just move it to the top of the
route, because is different from .
Personally I think the error message in 3.7.0 is more clear about this and
makes clear
Hi
What runtime are you using to run Camel, and it looks like your route
xml files are not spring xml files, but loaded via the new xml loader.
And if so then its a clue to it being the problem.
On Fri, Apr 9, 2021 at 10:10 AM HOEFLAKEN Jacob
wrote:
>
> Hi,
>
> I cannot add a doCatch anymore in
Hi Clause,
And yes, I am using route XML files.
Met vriendelijke groet / Kind regards,
Jacob Hoeflaken
Technology Leader
Tel: +31 88 988 90 00 - Mobiel: +31 6 11956482 - jacob.hoefla...@axians.com
-Original Message-
From: HOEFLAKEN Jacob
Sent: Friday, April 9, 2021 10:25
To:
Hi
Yes should be in the top of your route.
Camel will "fix" this internally, if you specify transacted in other parts.
On Fri, Apr 9, 2021 at 10:04 AM HOEFLAKEN Jacob
wrote:
>
> He,
>
> I have noticed some changes regarding the transacted element in 3.8.0/3.9.0
> in the XML DSL.
>
> In
He,
I have noticed some changes regarding the transacted element in 3.8.0/3.9.0 in
the XML DSL.
In 3.8.0+ I can specify the following:
http://0.0.0.0:8080"/>
${body}
I don't know of it
Hi,
I cannot add a doCatch anymore in the XML DSL since 3.8.0+.
http://camel.apache.org/schema/spring;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://camel.apache.org/schema/spring
https://camel.apache.org/schema/spring/camel-spring.xsd;>
Hi Clause,
I am using Camel Quarkus 1.8.0 (Camel 3.9) and 1.7.0 (Camel 3.8) moved back to
1.6.0 (Camel 3.7).
Met vriendelijke groet / Kind regards,
Jacob Hoeflaken
Technology Leader
Tel: +31 88 988 90 00 - Mobiel: +31 6 11956482 - jacob.hoefla...@axians.com
-Original Message-
Okay I have created a JIRA ticket
https://issues.apache.org/jira/browse/CAMEL-16476
--
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Hi George.
It appears that when we use the embedded ActiveMQ server, i.e. the vm protocol,
it will not negotiate a transaction with IBM MQ. The standalone ActiveMQ broker
seems to work.
Thank you for your help.
-Original Message-
From: George Daswani
Sent: Thursday, April 8, 2021
You don't have to specify grant_type. Your authentication failed. If you're
using password auth, make sure your password is actually password+API token.
On Thu, Apr 8, 2021 at 10:49 AM WEIQUAN YUAN wrote:
> It is proxy issue, now I moved application out of proxy env , the problem
> fixed.
> but
WEIQUAN YUAN14:10
Yes, I added configration here
camel.component.salesforce.http-proxy-host=cdhwg01.prod.prv
camel.component.salesforce.http-proxy-port=80
camel.component.salesforce.http-proxy-secure = true
but it gves me this error
Caused by: javax.net.ssl.SSLException: Unrecognized SSL
12 matches
Mail list logo
