public abstract class Permission extends Object implements Guard, Serializable
 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.
| Constructor and Description | 
|---|
| Permission(String name)Constructs a permission with the specified name. | 
| Modifier and Type | Method and Description | 
|---|---|
| abstract boolean | equals(Object obj)Checks two Permission objects for equality. | 
| abstract String | getActions()Returns the actions as a String. | 
| String | getName()Returns the name of this Permission. | 
| abstract int | hashCode()Returns the hash code value for this Permission object. | 
| abstract boolean | implies(Permission permission)Checks if the specified permission's actions are "implied by" this object's actions. | 
| String | toString()Returns a string describing this Permission. | 
public Permission(String name)
name - name of the Permission object being created.public abstract boolean equals(@Nullable Object obj)
 Do not use the equals method for making access control decisions; use the
 implies method.
equals in class Objectobj - the object we are testing for equality with this object.Object.hashCode(), 
HashMappublic 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 final String getName()
java.io.FilePermission, the name will be a pathname.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.
 hashCode in class ObjectObject.equals(java.lang.Object), 
System.identityHashCode(java.lang.Object)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.
permission - the permission to check against.public String toString()