Hi Team,
I have been using the Camel 2.24 in my application for some time and I was
trying to migrate the camel version from 2.24 to 3.4. The reason for this
migration is, the latest version has many great features in aggregate where
I am more interested like "AGGREGATION_COMPLETE_ALL_GROUPS" and
Use
exchange.adapt(ExtendedExchange.class).setNotifyEvent(true);
On Wed, Oct 28, 2020 at 3:28 PM tech tdeveloper
wrote:
>
> Hi Team,
>
> I have been using the Camel 2.24 in my application for some time and I was
> trying to migrate the camel version from 2.24 to 3.4. The reason for this
> migrat
On 2.x you can set the exchange property with key Exchange.REDELIVERY_EXHAUSTED
On Mon, Oct 26, 2020 at 4:44 PM Shenavai, Manuel
wrote:
>
> Hi Claus,
>
> thanks for providing a fix for this problem. The fix is available for 3.6.x
> codeline. We are running on 2.25.x codeline. Is there a chance t
Thank you
I have got dependencies
org.apache.camel
camel-http
${camel-version}
org.apache.camel
camel-soap
${camel-version}
org.apache.camel
camel-cxf
${camel-version}
I have tried add cxf-rt-transports-http-jetty but I have not luck. Exception
remains. (version 2.
You need to let Spring know about your bean, do Camel can find it. Now you are
self instantiating it and not registering anywhere.
From: Peter Turányi
Sent: 27 October 2020 08:20
To: users@camel.apache.org
Subject: RE: Camel CXF with SOAP 1.1 and SOAP 1.2
Thank
It took me a while to get cxf working in Java dsl also, and the way I did
it is like this:
CxfComponent cxfComponent = new CxfComponent(getContext());
CxfEndpoint serviceEndpoint = new CxfEndpoint("{{InputUrl}}", cxfComponent);
serviceEndpoint.setServiceClass(PortType.class);
serviceE
