Have there been any considerations to support SecurityManager's yet? There are a few places where code needs security permissions granted, when a SecurityManager is installed (e.g. ClassLoader creation, System.getProperty, AccessibleObject.setAccessible, ...).
This code should be wrapped in priviledged blocks then and an appropriate policy file should be provided for the different code bases. I know that (at least for stand-alone applications) SecurityManagers are rarely installed, but if so it's nice to have those priviledged blocks, otherwise permission(s) must be granted to the whole call stack. WDYT? _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
