Mirko, You seem to have a strange view of provisioning. It sounds like you startup a framework, load a bunch of bundles, hope for the best.
What should happen is: startup a framework, load a bundle that sets up your security policy using CPA, (you can delete that bundle now if you want the new policy will be persistent), load the rest of the bundles you want to run. It would be relatively easy to write an initial bundle that reads the default java policy file and populates the CPA that way, but I would think in general you want a policy that depends on the specific deployment or application rather than the Java install. (This is especially true when you are running multiple OSGi instances on the same machine.) Plus, the default java policy file does not allow you to express everything you can do with CPA. I'm not sure why you are talking about the StartLevelService. Is it because you didn't realize that the changes to policy done through the CPA are made persistent by the framework? ben _______________________________________________ OSGi Developer Mail List [email protected] http://www2.osgi.org/mailman/listinfo/osgi-dev
