public class MicroUIPermission extends Permission
MicroUI.start() and
MicroUI.stop()MicroUI.start(),
MicroUI.stop(),
Serialized Form| Modifier and Type | Field and Description |
|---|---|
static String |
ACTION_START
Action to start MicroUI.
|
static String |
ACTION_STOP
Action to stop MicroUI.
|
| Constructor and Description |
|---|
MicroUIPermission(String action)
Creates a permission for events generated by the given event generator with
null as name. |
| Modifier and Type | Method and Description |
|---|---|
boolean |
equals(Object obj)
Checks two Permission objects for equality.
|
String |
getActions()
Returns the actions as a String.
|
int |
hashCode()
Returns the hash code value for this Permission object.
|
boolean |
implies(Permission permission)
Checks if the specified permission's actions are "implied by" this object's actions.
|
getName, toStringpublic static final String ACTION_START
public static final String ACTION_STOP
public MicroUIPermission(String action)
null as name.action - the action to check.public boolean equals(@Nullable Object obj)
Permission
Do not use the equals method for making access control decisions; use the
implies method.
equals in class Permissionobj - the object we are testing for equality with this object.Object.hashCode(),
HashMappublic String getActions()
Permissionperm1 = new FilePermission(p1, "read,write"); perm2 = new FilePermission(p2, "write,read");both return "read,write" when the
getActions method is invoked.getActions in class Permissionpublic int hashCode()
Permission
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 PermissionObject.equals(java.lang.Object),
System.identityHashCode(java.lang.Object)public boolean implies(Permission permission)
PermissionThis must be implemented by subclasses of Permission, as they are the only ones that can impose semantics on a Permission object.
implies in class Permissionpermission - the permission to check against.