abstract public class: Permission
All Implemented Interfaces:
Abstract class for representing access to a system resource.
All permissions have a name (whose interpretation depends on the subclass),
as well as abstract functions for defining the semantics of the
particular Permission subclass.
Most Permission objects also include an "actions" list that tells the actions
that are permitted for the object. For example,
java.io.FilePermission object, the permission name is
the pathname of a file (or directory), and the actions list
(such as "read, write") specifies which actions are granted for the
specified file (or for files in the specified directory).
The actions list is optional for Permission objects, such as
that don't need such a list; you either have the named permission (such
as "system.exit") or you don't.
An important method that must be implemented by each subclass is
implies method to compare Permissions. Basically,
"permission p1 implies permission p2" means that
if one is granted permission p1, one is naturally granted permission p2.
Thus, this is not an equality test, but rather more of a
Permission objects are similar to String objects in that they
are immutable once they have been created. Subclasses should not
provide methods that can change the state of a permission
once it has been created.
public Permission(String name)
Constructs a permission with the specified name.
name - name of the Permission object being created.
|Methods from java.lang.Object:|
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait|
|Method from java.security.Permission Detail:|
public void checkGuard(Object object) throws SecurityException
Implements the guard interface for a permission. The
SecurityManager.checkPermission method is called,
passing this permission object as the permission to check.
Returns silently if access is granted. Otherwise, throws
abstract public boolean equals(Object obj)
abstract public String getActions()
Returns the actions as a String. This is abstract
so subclasses can defer creating a String representation until
one is needed. Subclasses should always return actions in what they
consider to be their
canonical form. For example, two FilePermission objects created via
perm1 = new FilePermission(p1,"read,write");
perm2 = new FilePermission(p2,"write,read");
"read,write" when the
getActions method is invoked.
public final String getName()
Returns the name of this Permission.
For example, in the case of a
the name will be a pathname.
abstract public int hashCode()
abstract public boolean implies(Permission permission)
Checks if the specified permission's actions are "implied by"
this object's actions.
This must be implemented by subclasses of Permission, as they are the
only ones that can impose semantics on a Permission object.
implies method is used by the AccessController to determine
whether or not a requested permission is implied by another permission that
is known to be valid in the current execution context.
public PermissionCollection newPermissionCollection()
Returns an empty PermissionCollection for a given Permission object, or null if
one is not defined. Subclasses of class Permission should
override this if they need to store their permissions in a particular
PermissionCollection object in order to provide the correct semantics
PermissionCollection.implies method is called.
If null is returned,
then the caller of this method is free to store permissions of this
type in any PermissionCollection they choose (one that uses a Hashtable,
one that uses a Vector, etc).
public String toString()
Returns a string describing this Permission. The convention is to
specify the class name, the permission name, and the actions in
the following format: '("ClassName" "name" "actions")', or
'("ClassName" "name")' if actions list is null or empty.