use Executors etc.
>
> Also, my threads will work accross bundles - simplest example is the
> whiteboard pattern, which calls code in any registered listener, in any
> bundle.
>
> Is the approach in this article the right way to go, to handle
> multithreading in OSGi? (ie. do y
lls code in any registered listener, in any
bundle.
Is the approach in this article the right way to go, to handle
multithreading in OSGi? (ie. do you use it?)
Are there other recommended approaches & best practices on how to manage
(start, stop, share) multiple threads in OSGi?
To avoid most of the
2 matches
Mail list logo
