This documentation differs from the official API.
Jadeite adds
extra features to the API including:
variable font sizes,
constructions examples,
placeholders for classes and methods, and auto-generated “See Also” links.
Additionally it
is missing some items found in standard Javadoc documentation, including:
generics type information,
“Deprecated” tags and comments,
“See Also” links,
along with other minor differences.
Please send any questions or feedback to
bam@cs.cmu.edu.
java.sql
class SQLPermission
- All Implemented Interfaces:
- Serializable, Guard
-
Most common way to construct:
-
SQLPermission SET_LOG_PERMISSION = new SQLPermission("setLog");
Based on 6 examples
public final class SQLPermission
extends BasicPermission
The permission for which the SecurityManager will check
when code that is running in an applet calls the
DriverManager.setLogWriter method or the
DriverManager.setLogStream (deprecated) method.
If there is no SQLPermission object, these methods
throw a java.lang.SecurityException as a runtime exception.
A SQLPermission object contains
a name (also referred to as a "target name") but no actions
list; there is either a named permission or there is not.
The target name is the name of the permission (see below). The
naming convention follows the hierarchical property naming convention.
In addition, an asterisk
may appear at the end of the name, following a ".", or by itself, to
signify a wildcard match. For example: loadLibrary.*
or * is valid,
but *loadLibrary or a*b is not valid.
The following table lists all the possible SQLPermission target names.
Currently, the only name allowed is setLog.
The table gives a description of what the permission allows
and a discussion of the risks of granting code the permission.
| Permission Target Name |
What the Permission Allows |
Risks of Allowing this Permission |
| setLog |
Setting of the logging stream |
This is a dangerous permission to grant.
The contents of the log may contain usernames and passwords,
SQL statements, and SQL data. |
The person running an applet decides what permissions to allow
and will run the Policy Tool to create an
SQLPermission in a policy file. A programmer does
not use a constructor directly to create an instance of SQLPermission
but rather uses a tool.
| Constructor Summary |
Creates a new SQLPermission object with the specified name.
|
Creates a new SQLPermission object with the specified name.
|
| Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
SQLPermission
public SQLPermission(String name)
-
Creates a new
SQLPermission object with the specified name.
The name is the symbolic name of the SQLPermission; currently,
the only name allowed is "setLog".
- Parameters:
name - the name of this SQLPermission object, which must
be setLog
SQLPermission
public SQLPermission(String name,
String actions)
-
Creates a new
SQLPermission object with the specified name.
The name is the symbolic name of the SQLPermission; the
actions String is currently unused and should be
null.
- Parameters:
name - the name of this SQLPermission object, which must
be setLogactions - should be null
This documentation differs from the official API.
Jadeite adds
extra features to the API including:
variable font sizes,
constructions examples,
placeholders for classes and methods, and auto-generated “See Also” links.
Additionally it
is missing some items found in standard Javadoc documentation, including:
generics type information,
“Deprecated” tags and comments,
“See Also” links,
along with other minor differences.
Please send any questions or feedback to
bam@cs.cmu.edu.
This page displays the
Jadeite version of the documention, which is derived from the offical documentation that contains this copyright notice:
The official Sun™ documentation can be found here at
http://java.sun.com/javase/6/docs/api/.
java.security.Permission