Dennis Reedy wrote:
That's what I was thinking, first make all the versioning information available
in metadata. The first potential OSGi service I can see is for the
net.jini.security.policy.DynamicPolicyProvider.
I'm currently reimplementing DynamicPolicyProvider for concurrency, in doing so
however it creates a dependency on Java 5. I'd like to keep the earlier
implementation for memory constrained or embedded environments such as Java 1.4
SE or cdc. So the DynamicPolicyProvider would be a good start. Although I'm
currently doing this using ServiceLoader SPI.
Why would versioning information aide in the loading of a
DynamicPolicyProvider? Why would you want to introduce an entire new technology
into the stack when you can use something as simple as the ServiceLoader to
obtain a DynamicPolicyProvider?
Bad example huh? What parts of the codebase do you think would benefit
from OSGi services?
