public abstract class BasicPermission extends Permission implements Serializable
The name for a BasicPermission is the name of the given permission (for example, "exit", "setFactory", "print.queueJob", etc). The naming convention follows the hierarchical property naming convention. An asterisk may appear by itself, or if immediately preceded by a "." may appear at the end of the name, to signify a wildcard match. For example, "*" and "java.*" signify a wildcard match, while "*java", "a*b", and "java*" do not.
The action string (inherited from Permission) is unused. Thus, BasicPermission is commonly used as the base class for "named" permissions (ones that contain a name but no actions list; you either have the named permission or you don't.) Subclasses may implement actions on top of BasicPermission, if desired.
Creates a new BasicPermission with the specified name.
Creates a new BasicPermission object with the specified name.
|Modifier and Type||Method||Description|
Checks two BasicPermission objects for equality.
Returns the canonical string representation of the actions, which currently is the empty string "", since there are no actions for a BasicPermission.
Returns the hash code value for this object.
Checks if the specified permission is "implied" by this object.
Returns a new PermissionCollection object for storing BasicPermission objects.
clone, finalize, getClass, notify, notifyAll, wait, wait, wait
public BasicPermission(String name)
public boolean implies(Permission p)
More specifically, this method returns true if:
p's class is the same as this object's class, and
p's name equals or (in the case of wildcards) is implied by this object's name. For example, "a.b.*" implies "a.b.c".
public boolean equals(Object obj)
obj's class is the same as this object's class and has the same name as this object.
public int hashCode()
getNameis from the Permission superclass.
public String getActions()
public PermissionCollection newPermissionCollection()
BasicPermission objects must be stored in a manner that allows them
to be inserted in any order, but that also enables the
to be implemented in an efficient (and consistent) manner.
Submit a bug or feature
For further API reference and developer documentation, see Java SE Documentation. That documentation contains more detailed, developer-targeted descriptions, with conceptual overviews, definitions of terms, workarounds, and working code examples.
Copyright © 1993, 2017, Oracle and/or its affiliates. 500 Oracle Parkway
Redwood Shores, CA 94065 USA. All rights reserved.