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
On Wed, Nov 29, 2023 at 9:06 PM Steve973 wrote:
> Hi, Claus. Thanks for the recommendation. Originally, I was going to use
> the RecipientList class and create an instance. I thought that I would see
> how core was creating the processor, which led me to my interest in the
> reifier class. Wh
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, Claus. You make a good point. I am setting up a helper class that
contains the code to create the RecipientList. I copied over everything
from the RecipientListReifier class, and converted the places that use the
Definition instances to just use my Configuration. I also removed the line
tha
Ok, I spoke too soon. I saw that the RecipientListProcessor has no trouble
with the Expression, and that means that I did not need the pipeline. So,
instead wrapping the expression evaluator and recipient list in a pipeline,
I skip that, and just return the Recipient List and it works as expected
Hello,
Currently, we replace the JCraft's Jsch library with com.hithub.mwiede:jsch
when we use org.apache.camel.springboot:camel-ftp-starter:4.2.0.
Does anyone know if there's a plan to implement sshd-mina instead in the
near future?
Our security team is a bit worried about downloading
com.hithu
Hi
There is no plans.
The jsch library is here and its 100% in the open (open source, BSD
license, home on github, etc)
https://github.com/mwiede/jsch
It is actively maintained and has more frequent releases.
And it's based on the jsch that is used in a lot of places.
And the FTP component has b
Hello. I am writing tests for my component with Spring, and configuring in
xml. How can I specify these values so that it looks in the header,
instead of interpreting these as literal string values?
Thanks,
Steve
Hi
That is just an endpoint, its not something evaluated for a given
exchange/message when being defined.
So you need to just configure them as string literals as-is.
So they have special meaning for your component. But what you do is wrong.
If you need dynamic uris in Camel then you use toD for
