Currently the whole config approach assumes that all the information is available in the whole ClassLoader/application.
If someone want's to guard against such an access, then this should best be done via the SecurityManager. But how to integrate this best?
Currently the whole config approach assumes that all the information is available in the whole ClassLoader/application.
If someone want's to guard against such an access, then this should best be done via the SecurityManager. But how to integrate this best?