> Don't know for the moment any drawbacks.
Thank you for your feedback Charles.
Any further thoughts related to the discussed design approach will be
appreciated :) .
--
Henryk Konsek
http://henryk-konsek.blogspot.com
Don't know for the moment any drawbacks.
On Tue, Feb 12, 2013 at 9:02 AM, Henryk Konsek wrote:
> Hi Charles,
>
> > What you suggest corresponds to what we have done for "direct-vm"
> component
>
> Yes, I'm aware that vm and vm-direct components handle static
> references. I'm just wondering if
Hi Charles,
> What you suggest corresponds to what we have done for "direct-vm" component
Yes, I'm aware that vm and vm-direct components handle static
references. I'm just wondering if this approach has any drawbacks or
corner cases (probably OSGI-related) I'm not aware of. I don't want to
reinv
Hi Henrik,
What you suggest corresponds to what we have done for "direct-vm" component
of camel (
https://github.com/apache/camel/blob/trunk/camel-core/src/main/java/org/apache/camel/component/directvm/DirectVmComponent.java)
where we use a static variable to register Consumer. This is not the cas
Hi,
I would like to have your opinion about sharing static members in the
Camel components.
Imagine the following scenario.
I want to create a Camel component that would be deployed on
ServiceMix. I want my component to cache some state and share it
between the ServiceMix bundles. For example I
