All Packages Class Hierarchy This Package Previous Next Index
java.lang.Object | +----java.security.Permission
Most Permission objects also include an "actions" list that tells the actions
that are permitted for the object. For example,
for a 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
java.lang.RuntimePermission
,
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
the 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
subset test.
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)
public void checkGuard(Object object) throws SecurityException
AccessController.checkPermission
method is called,
passing this permission object as the permission to check.
Returns silently if access is granted. Otherwise, throws
a SecurityException.
public abstract boolean implies(Permission permission)
This must be implemented by subclasses of Permission, as they are the only ones that can impose semantics on a Permission object.
The 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 abstract boolean equals(Object obj)
Do not use the equals
method for making access control
decisions; use the implies
method.
public abstract int hashCode()
The required hashCode
behavior for Permission Objects is
the following:
hashCode
method
must consistently return the same integer. This integer need not
remain consistent from one execution of an application to another
execution of the same application.
equals
method, then calling the hashCode
method on each of the
two Permission objects must produce the same integer result.
public final String getName()
java.io.FilePermission
,
the name will be a pathname.
public abstract String getActions()
perm1 = new FilePermission(p1,"read,write"); perm2 = new FilePermission(p2,"write,read");both return "read,write" when the
getActions
method is invoked.
public PermissionCollection newPermissionCollection()
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()
All Packages Class Hierarchy This Package Previous Next Index