public class RMISecurityManager extends SecurityManager
SecurityManagerused 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.
RMISecurityManagerdoes not apply to applets, which run under the protection of their browser's security manager.
RMISecurityManagerimplements a policy that is no different than the policy implemented by
SecurityManager. Therefore an RMI application should use the
SecurityManagerclass or another application-specific
SecurityManagerimplementation 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
main method of your application):
|Constructor and Description|
Constructs a new
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
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, 2013, Oracle and/or its affiliates. All rights reserved.