Connect to an HTTPS endpoint with self signed certificate

Hi all, I'm trying to connect to a HTTPS endpoint like http://camel.apache.org/schema/blueprint;> http://camel.apache.org/schema/blueprint; streamCache="true"> ... With this I'm getting an error “trustAnchors parameter must be non-empty” Both, keystore and truststore, are

Re: Upgrade to Camel Version Set ErrorHandler

Do you have any handy sample with you which I can refer to for this case? On Thu, Aug 10, 2023 at 2:34 PM Claus Ibsen wrote: > > Hi > > Read the javadoc of those methods what they do and just implement what you > need - its in the name also - supportsTransaction etc. > > On Thu, Aug 10, 2023 at

Re: Set UnitOfWorkFactory in CamelContext

thanks let me give it a try!! On Thu, Aug 10, 2023 at 2:37 PM Claus Ibsen wrote: > > context.getCamelContextExtension().addContextPlugin(UnitOfWorkFactory.class, > new MyUnitOfWorkFactory()); > > > On Thu, Aug 10, 2023 at 10:41 AM Kushagra Bindal > wrote: > > > Earlier we use to initiate the

Re: Set UnitOfWorkFactory in CamelContext

context.getCamelContextExtension().addContextPlugin(UnitOfWorkFactory.class, new MyUnitOfWorkFactory()); On Thu, Aug 10, 2023 at 10:41 AM Kushagra Bindal wrote: > Earlier we use to initiate the CamelContext object using below > mechanism. If you will notice that we use to set

Re: Upgrade to Camel Version Set ErrorHandler

Hi Read the javadoc of those methods what they do and just implement what you need - its in the name also - supportsTransaction etc. On Thu, Aug 10, 2023 at 10:29 AM Kushagra Bindal wrote: > Earlier the usage was to be like that as I mentioned here... We > usually checked on AsyncCallback and

Re: Set UnitOfWorkFactory in CamelContext

Earlier we use to initiate the CamelContext object using below mechanism. If you will notice that we use to set UnitOfWorkFactory, which is now not available neither in CamelContext nor into ExtendedCamelContext CamelContext camelContext = new SpringCamelContext(applicationContext);

Re: Upgrade to Camel Version Set ErrorHandler

Earlier the usage was to be like that as I mentioned here... We usually checked on AsyncCallback and reacted accordingly. @Override public Processor createErrorHandler(RouteContext routeContext, Processor processor) { return new DelegateAsyncProcessor(processor) { @Override

Re: Upgrade to Camel Version Set ErrorHandler

Why are you creating your own error handler implementation at all? What is special about it On Thu, Aug 10, 2023 at 10:05 AM Kushagra Bindal wrote: > Hi, > > I am trying to upgrade my camel version from 2.25.4 to 4.0.0.M3. > > Earlier I use to set ErrorHandler using below pattern. > >

Re: Set UnitOfWorkFactory in CamelContext

Thanks Claus for the quick response. I checked that already, and in the earlier version of Camel it use to have ExtendedCamelContext which usually contained the setUnitOfWorkFactory method. Please refer :

Upgrade to Camel Version Set ErrorHandler

Hi, I am trying to upgrade my camel version from 2.25.4 to 4.0.0.M3. Earlier I use to set ErrorHandler using below pattern. from(customString) .errorHandler(new RetrieveCustomErrorHandler()) .convertBodyTo(CustomRetrieve.class) .setProperty(JAXWS_METHOD_NAME_PROPERTY,

Re: Set UnitOfWorkFactory in CamelContext

Hi Read the migration guides https://camel.apache.org/manual/camel-4-migration-guide.html See the TIP in that api changes section On Thu, Aug 10, 2023 at 9:58 AM Kushagra Bindal wrote: > Hi, > > I am trying to upgrade my camel version from 2.25.4 to 4.0.0.M3. > > Earlier I use to set my

Set UnitOfWorkFactory in CamelContext

Hi, I am trying to upgrade my camel version from 2.25.4 to 4.0.0.M3. Earlier I use to set my UnitOfworkFactory using below pattern. camelContext.setUnitOfWorkFactory(customUnitOfWorkFactory); Now with the latest version of Camel, I just wanted to understand the new mechanism of doing the same.