public class RMISecurityManager extends SecurityManager
SecurityManager used by RMI applications that use
downloaded code. RMI's class loader will not download any classes from
remote locations if no security manager has been set.
RMISecurityManager does not apply to applets, which run
under the protection of their browser's security manager.
RMISecurityManager implements a policy that
is no different than the policy implemented by SecurityManager.
Therefore an RMI application should use the SecurityManager
class or another application-specific SecurityManager
implementation instead of this class.
To use a SecurityManager in your application, add
the following statement to your code (it needs to be executed before RMI
can download code from remote hosts, so it most likely needs to appear
in the main method of your application):
System.setSecurityManager(new SecurityManager());
inCheck| Constructor and Description |
|---|
RMISecurityManager()
Constructs a new
RMISecurityManager. |
checkAccept, checkAccess, checkAccess, checkAwtEventQueueAccess, checkConnect, checkConnect, checkCreateClassLoader, checkDelete, checkExec, checkExit, checkLink, checkListen, checkMemberAccess, checkMulticast, checkMulticast, checkPackageAccess, checkPackageDefinition, checkPermission, checkPermission, checkPrintJobAccess, checkPropertiesAccess, checkPropertyAccess, checkRead, checkRead, checkRead, checkSecurityAccess, checkSetFactory, checkSystemClipboardAccess, checkTopLevelWindow, checkWrite, checkWrite, classDepth, classLoaderDepth, currentClassLoader, currentLoadedClass, getClassContext, getInCheck, getSecurityContext, getThreadGroup, inClass, inClassLoader Submit a bug or feature
For further API reference and developer documentation, see Java SE Documentation. That documentation contains more detailed, developer-targeted descriptions, with conceptual overviews, definitions of terms, workarounds, and working code examples.
Copyright © 1993, 2011, Oracle and/or its affiliates. All rights reserved.
DRAFT ea-b138