java.security.Permission Maven / Gradle / Ivy
/*
This is not an official specification document, and usage is restricted.
NOTICE
(c) 2005-2007 Sun Microsystems, Inc. All Rights Reserved.
Neither this file nor any files generated from it describe a complete
specification, and they may only be used as described below. For
example, no permission is given for you to incorporate this file, in
whole or in part, in an implementation of a Java specification.
Sun Microsystems Inc. owns the copyright in this file and it is provided
to you for informative, as opposed to normative, use. The file and any
files generated from it may be used to generate other informative
documentation, such as a unified set of documents of API signatures for
a platform that includes technologies expressed as Java APIs. The file
may also be used to produce "compilation stubs," which allow
applications to be compiled and validated for such platforms.
Any work generated from this file, such as unified javadocs or compiled
stub files, must be accompanied by this notice in its entirety.
This work corresponds to the API signatures of JSR 219: Foundation
Profile 1.1. In the event of a discrepency between this work and the
JSR 219 specification, which is available at
http://www.jcp.org/en/jsr/detail?id=219, the latter takes precedence.
*/
package java.security;
/**
* 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,
* 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.
*
* @see Permissions
* @see PermissionCollection
*
* @version 1.35 00/02/02
*
* @author Marianne Mueller
* @author Roland Schemers
*/
public abstract class Permission implements Guard, java.io.Serializable
{
private String name;
/**
* Constructs a permission with the specified name.
*
* @param name name of the Permission object being created.
*
*/
public Permission(String name) { }
/**
* 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
* a SecurityException.
*
* @param object the object being guarded (currently ignored).
*
* @throws SecurityException
* if a security manager exists and its
* checkPermission method doesn't allow access.
*
* @see Guard
* @see GuardedObject
* @see SecurityManager#checkPermission
*
*/
public void checkGuard(Object object) throws SecurityException { }
/**
* 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.
*
*
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.
*
* @param permission the permission to check against.
*
* @return true if the specified permission is implied by this object,
* false if not.
*/
public abstract boolean implies(Permission permission);
/**
* Checks two Permission objects for equality.
*
* Do not use the equals method for making access control
* decisions; use the implies method.
*
* @param obj the object we are testing for equality with this object.
*
* @return true if both Permission objects are equivalent.
*/
public abstract boolean equals(Object obj);
/**
* Returns the hash code value for this Permission object.
*
* The required hashCode behavior for Permission Objects is
* the following:
*
* - Whenever it is invoked on the same Permission object more than
* once during an execution of a Java application, the
*
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.
*
- If two Permission objects are equal according to the
*
equals
* method, then calling the hashCode method on each of the
* two Permission objects must produce the same integer result.
*
*
* @return a hash code value for this object.
*/
public abstract int hashCode();
/**
* Returns the name of this Permission.
* For example, in the case of a java.io.FilePermission,
* the name will be a pathname.
*
* @return the name of this Permission.
*
*/
public final String getName() {
return null;
}
/**
* 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
* the following:
*
*
* perm1 = new FilePermission(p1,"read,write");
* perm2 = new FilePermission(p2,"write,read");
*
*
* both return
* "read,write" when the getActions method is invoked.
*
* @return the actions of this Permission.
*
*/
public abstract String getActions();
/**
* 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
* when the 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).
*
* @return a new PermissionCollection object for this type of Permission, or
* null if one is not defined.
*/
public PermissionCollection newPermissionCollection() {
return null;
}
/**
* 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")'.
*
* @return information about this Permission.
*/
public String toString() {
return null;
}
}