On 04/20/2012 04:52 PM, [email protected] wrote:
Looks nice!
Maybe there should be a way to avoid using exceptions to control whether we
load a class from classpath or from OSGi. For the best of my knowledge
throwing exceptions are time consuming due to the creation of the stack
trace.
I searched for an alternative when we started talking about it a few days
ago, but I could not find anything.
I now avoided to use Class.forName to check if OSGi is there.
The activator now sets a static variable to indicate if its running
inside OSGi or not. I also did some testing with OSGi and prepared
some documentation to explain how it can be used (still needs to be
committed).
Jörn
