This strikes me as a run-time dependency, not a compile time
dependency. Did I misunderstand what you meant?
Regards,
Alan
On 8/26/2005 12:40 PM, Richard S. Hall wrote:
The simplest example is that some of the classes in osgi.jar must
create instances of Filter, which is defined as an interface in
osgi.jar...thus they have to rely on the framework's impl class, which
is not known.
-> richard
Alan D. Cabrera wrote:
On 8/26/2005 11:01 AM, BJ Hargrave wrote:
Well it is not just for optimization. It is necessary for a
Framework impl to customize the OSGi supplied AdminPermission and
BundleSignerCondition classes. This is one of the reasons OSGi
releases this code under an OSL. Because we know that framework
impls MUST modify this code to hook into framework impl details.
For those of us who are not OSGi implementation gurus, could you
explain why these classes need to be customized? I did a *cursory*
glance through the spec and it's not clear to me.
There are other classes where customization is not necessary but
will be done for performance reasons. e.g FrameworkUtil.
I'll take a look at this. Thanks.
Regards,
Alan
