public Permission(String name) 
{
        this.name = name;
}

Constructs a permission with the specified name.

Parameters:

name - name of the Permission object being created.

 public  void checkGuard(Object object) throws SecurityException 
{
        SecurityManager sm = System.getSecurityManager();
        if (sm != null) sm.checkPermission(this);
}

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.

 abstract public boolean equals(Object obj)
Checks two Permission objects for equality.

Do not use the equals method for making access control
decisions; use the implies method.

 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
the following:

  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() 
{
        return name;
}

Returns the name of this Permission. For example, in the case of a java.io.FilePermission, the name will be a pathname.

 abstract public int hashCode()
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.

 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.

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 PermissionCollection newPermissionCollection() 
{
        return null;
}

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).

 public String toString() 
{
        String actions = getActions();
        if ((actions == null) || (actions.length() == 0)) { // OPTIONAL
            return "(\"" + getClass().getName() + "\" \"" + name + "\")";
        } else {
            return "(\"" + getClass().getName() + "\" \"" + name +
                 "\" \"" + actions + "\")";
        }
}

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.