Re: Shared static members in components

2013-02-12 Thread Henryk Konsek
> 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

Re: Shared static members in components

2013-02-12 Thread Charles Moulliard
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

Re: Shared static members in components

2013-02-12 Thread Henryk Konsek
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

Re: Shared static members in components

2013-02-11 Thread Charles Moulliard
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