Package Summary  Overview Summary

class:SQLPermission [CHANGED]

  • All Implemented Interfaces:
    java.io.Serializable, java.security.Guard


    public final class SQLPermission
    extends java.security.BasicPermission
    The permission for which the SecurityManager will check when code that is running in an applet, oran application with a SecurityManager enabled, calls the DriverManager.deregisterDriver method, DriverManager.setLogWriter method, DriverManager.setLogStream (deprecated) method, SyncFactory.setJNDIContext method, SyncFactory.setLogger method, Connection.setNetworktimeout method, or the Connection.abort 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, butand * signify a wildcard match, while *loadLibrary orand a*b isdo not valid.

    The following table lists all the possible SQLPermission target names. 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
    setLogSetting 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.
    callAbortAllows the invocation of the Connection method abort Permits an application to terminate a physical connection to a database.
    setSyncFactoryAllows the invocation of the SyncFactory methods setJNDIContext and setLogger Permits an application to specify the JNDI context from which the SyncProvider implementations can be retrieved from and the logging object to be used by the SyncProvider implementation.
    setNetworkTimeoutAllows the invocation of the Connection method setNetworkTimeout Permits an application to specify the maximum period a Connection or objects created from the Connection will wait for the database to reply to any one request.
    The person runningderegisterDriver Allows the invocation of the DriverManager method deregisterDriver Permits an applet decides what permissionsapplication to allow and will runremove a JDBC driver from the Policy Tool to create an SQLPermission in a policy file. A programmer does not use a constructor directly to create an instancelist of SQLPermission but rather uses a toolregistered Drivers and release its resources.

    Since:
    1.3
    See Also:
    <code>BasicPermission</code>, <code>Permission</code>, <code>Permissions</code>, <code>PermissionCollection</code>, <code>SecurityManager</code>, Serialized Form
  • All Implemented Interfaces:
    java.io.Serializable, java.security.Guard


    public final class SQLPermission
    extends java.security.BasicPermission
    The permission for which the SecurityManager will check when code that is running in an applet, or an application with a SecurityManager enabled, calls the DriverManager.setLogWriter method, DriverManager.setLogStream (deprecated) method, SyncFactory.setJNDIContext method, SyncFactory.setLogger method, Connection.setNetworktimeout method, or the Connection.abort 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. 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
    setLogSetting 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.
    callAbortAllows the invocation of the Connection method abort Permits an application to terminate a physical connection to a database.
    setSyncFactoryAllows the invocation of the SyncFactory methods setJNDIContext and setLogger Permits an application to specify the JNDI context from which the SyncProvider implementations can be retrieved from and the logging object to be used by the SyncProvider implementation.
    setNetworkTimeoutAllows the invocation of the Connection method setNetworkTimeout Permits an application to specify the maximum period a Connection or objects created from the Connection will wait for the database to reply to any one request.

    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.

    Since:
    1.3
    See Also:
    <code>BasicPermission</code>, <code>Permission</code>, <code>Permissions</code>, <code>PermissionCollection</code>, <code>SecurityManager</code>, Serialized Form
  • All Implemented Interfaces:
    java.io.Serializable, java.security.Guard


    public final class SQLPermission
    extends java.security.BasicPermission
    The permission for which the SecurityManager will check when code that is running an application with a SecurityManager enabled, calls the DriverManager.deregisterDriver method, DriverManager.setLogWriter method, DriverManager.setLogStream (deprecated) method, SyncFactory.setJNDIContext method, SyncFactory.setLogger method, Connection.setNetworktimeout method, or the Connection.abort 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.* and * signify a wildcard match, while *loadLibrary and a*b do not.

    The following table lists all the possible SQLPermission target names. 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
    setLogSetting 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.
    callAbortAllows the invocation of the Connection method abort Permits an application to terminate a physical connection to a database.
    setSyncFactoryAllows the invocation of the SyncFactory methods setJNDIContext and setLogger Permits an application to specify the JNDI context from which the SyncProvider implementations can be retrieved from and the logging object to be used by the SyncProvider implementation.
    setNetworkTimeoutAllows the invocation of the Connection method setNetworkTimeout Permits an application to specify the maximum period a Connection or objects created from the Connection will wait for the database to reply to any one request.
    deregisterDriverAllows the invocation of the DriverManager method deregisterDriver Permits an application to remove a JDBC driver from the list of registered Drivers and release its resources.

    Since:
    1.3
    See Also:
    <code>BasicPermission</code>, <code>Permission</code>, <code>Permissions</code>, <code>PermissionCollection</code>, <code>SecurityManager</code>, Serialized Form

constructor:SQLPermission(java.lang.String) [NONE]

  • SQLPermission

    public SQLPermission(java.lang.String name)
    Creates a new SQLPermission object with the specified name. The name is the symbolic name of the SQLPermission.
    Parameters:
    name - the name of this SQLPermission object, which must be either setLog, callAbort, setSyncFactory, or setNetworkTimeout
    Throws:
    java.lang.NullPointerException - if name is null.
    java.lang.IllegalArgumentException - if name is empty.

constructor:SQLPermission(java.lang.String, java.lang.String) [NONE]

  • SQLPermission

    public SQLPermission(java.lang.String name,
                         java.lang.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 either setLog, callAbort, setSyncFactory, or setNetworkTimeout
    actions - should be null
    Throws:
    java.lang.NullPointerException - if name is null.
    java.lang.IllegalArgumentException - if name is empty.