Docjar: A Java Source and Docuemnt Enginecom.*    java.*    javax.*    org.*    all    new    plug-in

Quick Search    Search Deep
Home >> All >> org >> apache >> derby >> impl >> [ jdbc Javadoc ]

•org.apache.derby.impl.jdbc.authentication.* (7)

• org.apache.derby.impl.jdbc: Javadoc index of package org.apache.derby.impl.jdbc.


Package Samples:

• org.apache.derby.impl.jdbc.authentication

Classes:

• TransactionResourceImpl: An instance of a TransactionResourceImpl is a bundle of things that connects a connection to the database - it is the transaction "context" in a generic sense. It is also the object of synchronization used by the connection object to make sure only one thread is accessing the underlying transaction and context. TransactionResourceImpl not only serves as a transaction "context", it also takes care of: context management: the pushing and popping of the context manager in and out of the global context service transaction demarcation: all calls to commit/abort/prepare/close a transaction must route ...
• EmbedDatabaseMetaData: This class provides information about the database as a whole. Many of the methods here return lists of information in ResultSets. You can use the normal ResultSet methods such as getString and getInt to retrieve the data from these ResultSets. If a given form of metadata is not available, these methods should throw a SQLException. Some of these methods take arguments that are String patterns. These arguments all have names such as fooPattern. Within a pattern String, "%" means match any substring of 0 or more characters, and "_" means match any one character. Only metadata entries matching the ...
• EmbedBlob: Implements java.sql.Blob (see the JDBC 2.0 spec). A blob sits on top of a BINARY, VARBINARY or LONG VARBINARY column. If its data is small (less than 1 page) it is a byte array taken from the SQLBit class. If it is large (more than 1 page) it is a long column in the database. The long column is accessed as a stream, and is implemented in store as an OverflowInputStream. The Resetable interface allows sending messages to that stream to initialize itself (reopen its container and lock the corresponding row) and to reset itself to the beginning. NOTE: In the case that the data is large, it is represented ...
• EmbedClob: Implements java.sql.Clob (see the JDBC 2.0 spec). A clob sits on top of a CHAR, VARCHAR or LONG VARCHAR column. If its data is small (less than 1 page) it is a byte array taken from the SQLChar class. If it is large (more than 1 page) it is a long column in the database. The long column is accessed as a stream, and is implemented in store as an OverflowInputStream. The Resetable interface allows sending messages to that stream to initialize itself (reopen its container and lock the corresponding row) and to reset itself to the beginning. NOTE: In the case that the data is large, it is represented ...
• LDAPAuthenticationSchemeImpl: This is the Cloudscape LDAP authentication scheme implementation. JNDI system/environment properties can be set at the database level as database properties. They will be picked-up and set in the JNDI initial context if any are found. We do connect first to the LDAP server in order to retrieve the user's distinguished name (DN) and then we reconnect and try to authenticate with the user's DN and passed-in password. In 2.0 release, we first connect to do a search (user full DN lookup). This initial lookup can be done through anonymous bind or using special LDAP search credentials that the user may ...
• EmbedConnection: Local implementation of Connection for a JDBC driver in the same process as the database. There is always a single root (parent) connection. The initial JDBC connection is the root connection. A call to getCurrentConnection() or with the URL jdbc:default:connection yields a nested connection that shares the same root connection as the parent. A nested connection is implemented using this class. The nested connection copies the state of the parent connection and shares some of the same objects (e.g. ContextManager) that are shared across all nesting levels. The proxy also maintains its own state ...
• EmbedParameterSetMetaData: This class immitates to implement the ParameterMetaData interface from JDBC3.0 We want to provide the functionality to JDKs before JDBC3.0. We put it here instead of in Local20 because we want to make it available for CallableStatement. It provides the parameter meta data for callable & prepared statements. The subclass in Local30 actually implements ParameterMetaData interface. Our middle-tier servers or tools (eg. drda network server) can use it this way: import org.apache.derby.impl.jdbc.EmbedPreparedStatement; import org.apache.derby.impl.jdbc.EmbedParameterSetMetaData; EmbedParameterSetMetaData ...
• AuthenticationServiceBase: This is the authentication service base class. There can be 1 Authentication Service for the whole Cloudscape system and/or 1 authentication per database. In a near future, we intend to allow multiple authentication services per system and/or per database. It should be extended by the specialized authentication services. IMPORTANT NOTE: -------------- User passwords are encrypted using SHA-1 message digest algorithm if they're stored in the database; otherwise they are not encrypted if they were defined at the system level. SHA-1 digest is single hash (one way) digest and is considered very secure ...
• EmbedConnection30: This class extends the EmbedConnection20 class in order to support new methods and classes that come with JDBC 3.0. Supports JSR169 - Subsetting only removes getTypeMap and setTypeMap, which references java.util.Map which exists in Foundation and ee.miniumum. Thus the methods can safely be left in the implementation for JSR169. JDBC 3.0 - Separate from JDBC 2.0 implementation as JDBC 3.0 introduces a new class java.sql.Savepoint, which is referenced by java.sql.Connection.
• EmbedSavepoint30: This class implements the Savepoint interface from JDBC3.0 This allows to set, release, or rollback a transaction to designated Savepoints. Savepoints provide finer-grained control of transactions by marking intermediate points within a transaction. Once a savepoint has been set, the transaction can be rolled back to that savepoint without affecting preceding work. Supports JSR169 - no subsetting for java.sql.Savepoint JDBC 3.0 - class introduced in JDBC 3.0
• BasicAuthenticationServiceImpl: This authentication service is the basic Cloudscape User authentication level support. It is activated upon setting derby.authentication.provider database or system property to 'BUILTIN'. It instantiates & calls the basic User authentication scheme at runtime. In 2.0, users can now be defined as database properties. If derby.database.propertiesOnly is set to true, then in this case, only users defined as database properties for the current database will be considered.
• EmbedSQLWarning: This class understands the message protocol and looks up SQLExceptions based on keys, so that the Local JDBC driver's messages can be localized. REMIND: May want to investigate putting some of this in the protocol side, for the errors that any Cloudscape JDBC driver might return. The ASSERT mechanism is a wrapper of the basic services, to ensure that failed asserts at this level will behave well in a JDBC environment.
• Util: This class understands the message protocol and looks up SQLExceptions based on keys, so that the Local JDBC driver's messages can be localized. REMIND: May want to investigate putting some of this in the protocol side, for the errors that any Cloudscape JDBC driver might return. The ASSERT mechanism is a wrapper of the basic services, to ensure that failed asserts at this level will behave well in a JDBC environment.
• EmbedSQLException: This class is what gets send over the wire in client/server configuration. When running embedded, this has the detailed stack trace for exceptions. In case of client/server, server has all the stack trace information but client doesn't get the stack trace, just the sql exception. The reason for this implementation is the stack trace information is more relevant on the server side and it also decreases the size of client jar file tremendously.
• EmbedCallableStatement169: CallableStatement implementation for JSR169. Adds no functionality to its (abstract) parent class. If Derby could be compiled against JSR169 that the parent class could be the concrete class for the environment. Just like for the JDBC 2.0 specific classes. Until that is possible (ie. easily downloadable J2ME/CDC/Foundation/JSR169 jar files, this class is required and is only compiled by an optional target. Supports JSR 169
• EmbedPreparedStatement169: PreparedStatement implementation for JSR169. Adds no functionality to its (abstract) parent class. If Derby could be compiled against JSR169 that the parent class could be the concrete class for the environment. Just like for the JDBC 2.0 specific classes. Until that is possible (ie. easily downloadable J2ME/CDC/Foundation/JSR169 jar files, this class is required and is only compiled by an optional target. Supports JSR 169
• EmbedResultSet169: ResultSet implementation for JSR169. Adds no functionality to its (abstract) parent class. If Derby could be compiled against JSR169 that the parent class could be the concrete class for the environment. Just like for the JDBC 2.0 specific classes. Until that is possible (ie. easily downloadable J2ME/CDC/Foundation/JSR169 jar files, this class is required and is only compiled by an optional target. Supports JSR 169
• EmbedParameterMetaData30: This class implements the ParameterMetaData interface from JDBC3.0 It provides the parameter meta data for callable & prepared statements But note that the bulk of it resides in its parent class. The reason is we want to provide the functionality to the JDKs before JDBC3.0. Supports JDBC 3.0 - java.sql.ParameterMetaData introduced in JDBC3
• EmbedResultSetMetaData: A ResultSetMetaData object can be used to find out about the types and properties of the columns in a ResultSet. We take the (cloudscape) ResultDescription and examine it, to return the appropriate information. This class can be used outside of this package to convert a ResultDescription into a ResultSetMetaData object.
• JNDIAuthenticationService: This is the JNDI Authentication Service base class. It instantiates the JNDI authentication scheme defined by the user/ administrator. Cloudscape supports LDAP JNDI providers. The user can configure its own JNDI provider by setting the system or database property derby.authentication.provider .
• EmbedStatement: EmbedStatement is a local JDBC statement. Supports JSR169 - no subsetting for java.sql.Statement JDBC 2.0 JDBC 3.0 - no new dependencies on new JDBC 3.0 or JDK 1.4 classes, new methods can safely be added into implementation.
• NoneAuthenticationServiceImpl: This authentication service does not care much about authentication. It is a quiescient authentication service that will basically satisfy any authentication request, as JBMS system was not instructed to have any particular authentication scheme to be loaded at boot-up time.
• EmbedPreparedStatement30: This class extends the EmbedPreparedStatement20 class in order to support new methods and classes that come with JDBC 3.0. Supports JDBC 3.0 - dependency on java.sql.ParameterMetaData introduced in JDBC 3.0
• EmbedCallableStatement30: This class extends the EmbedCallableStatement20 in order to support new methods and classes that come with JDBC 3.0. Supports JDBC 3.0 - dependency on java.sql.ParameterMetaData introduced in JDBC 3.0
• JNDIAuthenticationSchemeBase: This is the base JNDI authentication scheme class. The generic environment JNDI properties for the selected JNDI scheme are retrieved here so that the user can set JNDI properties at the database or system level.

Home | Contact Us | Privacy Policy | Terms of Service