W3cubDocs

/OpenJDK 8

Class LoggingPermission

All Implemented Interfaces:
Serializable, Guard
public final class LoggingPermission
extends BasicPermission

The permission which the SecurityManager will check when code that is running with a SecurityManager calls one of the logging control methods (such as Logger.setLevel).

Currently there is only one named LoggingPermission. This is "control" and it grants the ability to control the logging configuration, for example by adding or removing Handlers, by adding or removing Filters, or by changing logging levels.

Programmers do not normally create LoggingPermission objects directly. Instead they are created by the security policy code based on reading the security policy file.

Since:
1.4
See Also:
BasicPermission, Permission, Permissions, PermissionCollection, SecurityManager, Serialized Form

Constructors

LoggingPermission

public LoggingPermission(String name,
                         String actions)
                  throws IllegalArgumentException

Creates a new LoggingPermission object.

Parameters:
name - Permission name. Must be "control".
actions - Must be either null or the empty string.
Throws:
NullPointerException - if name is null.
IllegalArgumentException - if name is empty or if arguments are invalid.

Methods

Methods inherited from class java.security.BasicPermission

equals, getActions, hashCode, implies, newPermissionCollection

Methods inherited from class java.security.Permission

checkGuard, getName, toString

Methods inherited from class java.lang.Object

clone, finalize, getClass, notify, notifyAll, wait, wait, wait

© 1993–2017, Oracle and/or its affiliates. All rights reserved.
Documentation extracted from Debian's OpenJDK Development Kit package.
Licensed under the GNU General Public License, version 2, with the Classpath Exception.
Various third party code in OpenJDK is licensed under different licenses (see Debian package).
Java and OpenJDK are trademarks or registered trademarks of Oracle and/or its affiliates.