- java.lang.Object
-
- java.security.Permission
-
- All Implemented Interfaces:
- Serializable, Guard
- Direct Known Subclasses:
- AllPermission, BasicPermission, FilePermission, MBeanPermission, PrivateCredentialPermission, ServicePermission, SocketPermission, UnresolvedPermission
public abstract class Permission extends Object implements Guard, Serializable
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 asjava.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 Also:
Permissions
,PermissionCollection
, Serialized Form
-
-
Constructor Summary
Constructors Constructor and Description Permission(String name)
Constructs a permission with the specified name.
-
Method Summary
Methods Modifier and Type Method and Description void
checkGuard(Object object)
Implements the guard interface for a permission.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.PermissionCollection
newPermissionCollection()
Returns an empty PermissionCollection for a given Permission object, or null if one is not defined.String
toString()
Returns a string describing this Permission.
-
-
-
Constructor Detail
-
Permission
public Permission(String name)
Constructs a permission with the specified name.- Parameters:
name
- name of the Permission object being created.
-
-
Method Detail
-
checkGuard
public void checkGuard(Object object) throws SecurityException
Implements the guard interface for a permission. TheSecurityManager.checkPermission
method is called, passing this permission object as the permission to check. Returns silently if access is granted. Otherwise, throws a SecurityException.- Specified by:
checkGuard
in interfaceGuard
- Parameters:
object
- the object being guarded (currently ignored).- Throws:
SecurityException
- if a security manager exists and itscheckPermission
method doesn't allow access.- See Also:
Guard
,GuardedObject
,SecurityManager.checkPermission(java.security.Permission)
-
implies
public abstract 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.- Parameters:
permission
- the permission to check against.- Returns:
- true if the specified permission is implied by this object, false if not.
-
equals
public abstract boolean equals(Object obj)
Checks two Permission objects for equality.Do not use the
equals
method for making access control decisions; use theimplies
method.- Overrides:
equals
in classObject
- Parameters:
obj
- the object we are testing for equality with this object.- Returns:
- true if both Permission objects are equivalent.
- See Also:
Object.hashCode()
,HashMap
-
hashCode
public abstract 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 thehashCode
method on each of the two Permission objects must produce the same integer result.
- Overrides:
hashCode
in classObject
- Returns:
- a hash code value for this object.
- See Also:
Object.equals(java.lang.Object)
,System.identityHashCode(java.lang.Object)
- Whenever it is invoked on the same Permission object more than
once during an execution of a Java application, the
-
getName
public final String getName()
Returns the name of this Permission. For example, in the case of ajava.io.FilePermission
, the name will be a pathname.- Returns:
- the name of this Permission.
-
getActions
public abstract 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 thegetActions
method is invoked.- Returns:
- the actions of this Permission.
-
newPermissionCollection
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 when thePermissionCollection.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).- Returns:
- a new PermissionCollection object for this type of Permission, or null if one is not defined.
-
toString
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.
-
-
Deutsche Übersetzung
Sie haben gebeten, diese Seite auf Deutsch zu besuchen. Momentan ist nur die Oberfläche übersetzt, aber noch nicht der gesamte Inhalt.Wenn Sie mir bei Übersetzungen helfen wollen, ist Ihr Beitrag willkommen. Alles, was Sie tun müssen, ist, sich auf der Website zu registrieren und mir eine Nachricht zu schicken, in der Sie gebeten werden, Sie der Gruppe der Übersetzer hinzuzufügen, die Ihnen die Möglichkeit gibt, die gewünschten Seiten zu übersetzen. Ein Link am Ende jeder übersetzten Seite zeigt an, dass Sie der Übersetzer sind und einen Link zu Ihrem Profil haben.
Vielen Dank im Voraus.
Dokument erstellt 11/06/2005, zuletzt geändert 04/03/2020
Quelle des gedruckten Dokuments:https://www.gaudry.be/de/java-api-rf-java/security/Permission.html
Die Infobro ist eine persönliche Seite, deren Inhalt in meiner alleinigen Verantwortung liegt. Der Text ist unter der CreativeCommons-Lizenz (BY-NC-SA) verfügbar. Weitere Informationen auf die Nutzungsbedingungen und dem Autor.
Referenzen
Diese Verweise und Links verweisen auf Dokumente, die während des Schreibens dieser Seite konsultiert wurden, oder die zusätzliche Informationen liefern können, aber die Autoren dieser Quellen können nicht für den Inhalt dieser Seite verantwortlich gemacht werden.
Der Autor Diese Website ist allein dafür verantwortlich, wie die verschiedenen Konzepte und Freiheiten, die mit den Nachschlagewerken gemacht werden, hier dargestellt werden. Denken Sie daran, dass Sie mehrere Quellinformationen austauschen müssen, um das Risiko von Fehlern zu reduzieren.