Thanks, Claus. The BeanScope.Request option seems to have fixed that
part. Thanks!
On Sun, Dec 3, 2023 at 3:30 AM Claus Ibsen wrote:
> Hi
>
> A route or processor will often lookup the bean once and use that same
> instance all the time.
>
> The bind/unbind is not intended for dynamic.
>
> How
Hi
A route or processor will often lookup the bean once and use that same
instance all the time.
The bind/unbind is not intended for dynamic.
However the bean component has a cache option you can set to lookup always.
A processor does not.
On Sun, Dec 3, 2023 at 12:52 AM Steve973 wrote:
> He
Hello. I am binding a processor in the registry, which works fine. At
some point, I unbind it, and then bind a different processor with the same
bean name. I am even printing out the class name after I bind, in order to
verify it.
The first print shows the original/temporary processor.
After u
