I guess there are several ways to do this but the most portable one should be to start with security enabled (and in felix case - the framework.security bundle installed). From there, you could specify a policy that gives allpermission but has a deny on System.Exit.
Assuming you don't have a lot of osgi security knowledge I can try to write a more detailed mail about how to do this tonight... regards, Karl On Mon, Oct 4, 2010 at 12:45 PM, Achim Nierbeck <[email protected]> wrote: > Hi, > > I asked this question in the karaf user mailing list but they told me this > would be the better place to ask :) > I have a special Problem I would like to solve with the SecurityManger. But > first the Problem I'm facing: > I have a bundle containing a third party legacy library I have to use. > This Library does call system.Exit(?) if it looses it's connection to a > corresponding server. > I know that this is really bad (actually mean) but the quickest way of > shipping around this problem is using a service wrapper which does a > restart. > But this is not a nice way of doing especially this system.exit forces a > hard shutdown :( > So I googled around and found that there is one solution for this, use a > security manager which disallows System.Exit. > Now the tricky part, how do I specify a securityManager just for this bundle > preventing it from using System.Exit? > > Thank you in Advance :) > -- Karl Pauls [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
