Re: Refreshing Bean To Build An IMAP Route Should Have Worked

2025-03-04 Thread Dipak Rai
Hi Riccardo, Thank you so much for your answers on my thread request. I have already kept my Route building logic in a separate class. And only to build the IMAP *from *route dynamically I have a separate method *getImapConfig .* After putting some log statements and checking the hashcode of the

[ANNOUNCE] Apache Camel 4.10.1 (LTS) Released

2025-03-04 Thread Gregor Zurowski
The Camel PMC is pleased to announce the release of Apache Camel 4.10.1 (LTS). Apache Camel is an open source integration framework that empowers you to quickly and easily integrate various systems consuming or producing data. This release contains 40 bug fixes and improvements. The release is a

Re: Refreshing Bean To Build An IMAP Route Should Have Worked

2025-03-04 Thread Modanese, Riccardo
Hi, you should proceed splitting the implementation in 2 components. Implement your own org.apache.camel.builder.RouteBuilder to create routes Implement your own org.springframework.beans.factory.support.BeanDefinitionRegistryPostProcessor to inject beans in the context Without Spring the

Re: Refreshing Bean To Build An IMAP Route Should Have Worked

2025-03-04 Thread Dipak Rai
Also the registry.unbind() says "Removes the bean from the repository (if possible)." What does this "if possible" means here? On Tue, Mar 4, 2025 at 10:07 PM Dipak Rai wrote: > The registry.bind () documentation says that "*Binds the bean to the > repository (if possible). If the bean is CamelC

Re: Refreshing Bean To Build An IMAP Route Should Have Worked

2025-03-04 Thread Dipak Rai
The registry.bind () documentation says that "*Binds the bean to the repository (if possible). If the bean is CamelContextAware then the registry will automatic inject the context if possible."* What does that mean ? How can I make the 'exchangeAuthenticator' bean CamelContextAware? On Tue, Mar 4

Re: Refreshing Bean To Build An IMAP Route Should Have Worked

2025-03-04 Thread Dipak Rai
Hi, To add to my code snippet, I see in the logs that I could unbind the bean and rebind it but somehow in the route url this string *"?authenticator=#exchangeAuthenticator" *does not show the updated values. I still get the error for the wrong *tenantID *I passed deliberately before last tim *e.*

Re: Refreshing Bean To Build An IMAP Route Should Have Worked

2025-03-04 Thread Dipak Rai
Hi, Yes, Riccardo. //code snippet removing the route before recreating the authenticator bean Route route = camelContext.getRoute(MyConstants.IMAP_ROUTE_ID); if (route != null) { camelContext.getRouteController().stopRoute(MyConstants.IMAP_ROUTE_ID); camelContext.removeRoute(MyConstants.IMAP_ROUT

[ANNOUNCE] Apache Camel 4.8.4 (LTS) Released

2025-03-04 Thread Gregor Zurowski
The Camel PMC is pleased to announce the release of Apache Camel 4.8.4 (LTS). Apache Camel is an open source integration framework that empowers you to quickly and easily integrate various systems consuming or producing data. This release contains 35 bug fixes and improvements. The release is av

Re: Refreshing Bean To Build An IMAP Route Should Have Worked

2025-03-04 Thread Modanese, Riccardo
Hi, I’ injecting beans at runtime using Camel with and without Spring (and it works) but, I did it before starting the route. From my understanding you are trying to replace a bean in the context once the route is running, am I right? If so, did you try to restart the route once y

Re: Refreshing Bean To Build An IMAP Route Should Have Worked

2025-03-04 Thread Dipak Rai
I'll rephrase my question here. Is it possible to just kick out the old bean from the Camel Context (and in turn from the Spring context) and inject a new bean while using the same to build a route dynamically as shown below? I don't see any explicit ' *unbind()*' method with the *ApplicationContex