Home >> All >> org >> apache >> geronimo >> [ connector Javadoc ]

•	org.apache.geronimo.connector.deployment.* (20)	•	org.apache.geronimo.connector.mock.* (13)
•	org.apache.geronimo.connector.outbound.* (61)	•	org.apache.geronimo.connector.work.* (11)

• org.apache.geronimo.connector: Javadoc index of package org.apache.geronimo.connector.


Package Samples:

• org.apache.geronimo.connector.deployment
• org.apache.geronimo.connector.mock
• org.apache.geronimo.connector.deployment.dconfigbean
• org.apache.geronimo.connector.outbound
• org.apache.geronimo.connector.outbound.connectiontracking
• org.apache.geronimo.connector.work
• org.apache.geronimo.connector.outbound.connectionmanagerconfig
• org.apache.geronimo.connector.outbound.transactionlog
• org.apache.geronimo.connector.outbound.security
• org.apache.geronimo.connector.work.pool

Classes:

• TransactionCachingInterceptor: TransactionCachingInterceptor.java TODO: This implementation does not take account of unshareable resources TODO: This implementation does not take account of application security where several connections with different security info are obtained. TODO: This implementation does not take account of container managed security where, within one transaction, a security domain boundary is crossed and connections are obtained with two (or more) different subjects. I suggest a state pattern, with the state set in a threadlocal upon entering a component, will be a usable implementation. The afterCompletion ...
• ConnectionTrackingCoordinator: ConnectionTrackingCoordinator tracks connections that are in use by components such as EJB's. The component must notify the ccm when a method enters and exits. On entrance, the ccm will notify ConnectionManager stacks so the stack can make sure all connection handles left open from previous method calls are attached to ManagedConnections of the correct security context, and the ManagedConnections are enrolled in any current transaction. On exit, the ccm will notify ConnectionManager stacks of the handles left open, so they may be disassociated if appropriate. In addition, when a UserTransaction ...
• SinglePoolConnectionInterceptor: SinglePoolConnectionInterceptor chooses a single connection from the pool. If selectOneAssumeMatch is true, it simply returns the selected connection. THIS SHOULD BE USED ONLY IF MAXIMUM SPEED IS ESSENTIAL AND YOU HAVE THOROUGLY CHECKED THAT MATCHING WOULD SUCCEED ON THE SELECTED CONNECTION. (i.e., read the docs on your connector to find out how matching works) If selectOneAssumeMatch is false, it checks with the ManagedConnectionFactory that the selected connection does match before returning it: if not it throws an exception.
• SinglePoolMatchAllConnectionInterceptor: This pool is the most spec-compliant pool. It can be used by itself with no partitioning. It is apt to be the slowest pool. For each connection request, it synchronizes access to the pool and asks the ManagedConnectionFactory for a match from among all managed connections. If none is found, it may discard a random existing connection, and creates a new connection.
• GeronimoWorkManager: WorkManager implementation which uses under the cover three WorkExecutorPool - one for each synchronization policy - in order to dispatch the submitted Work instances. A WorkManager is a component of the JCA specifications, which allows a Resource Adapter to submit tasks to an Application Server for execution.
• ConnectionTrackingInterceptor: ConnectionTrackingInterceptor.java handles communication with the CachedConnectionManager. On method call entry, cached handles are checked for the correct Subject. On method call exit, cached handles are disassociated if possible. On getting or releasing a connection the CachedConnectionManager is notified.
• MultiPoolConnectionInterceptor: MultiPoolConnectionInterceptor maps the provided subject and connection request info to a "SinglePool". This can be used to make sure all matches will succeed, avoiding synchronization slowdowns. Created: Fri Oct 10 12:53:11 2003
• JDBCLog: "Last Resource optimization" for single servers wishing to have valid xa transactions with a single 1-pc datasource. The database is used for the log, and the database work is committed when the log writes its prepare record.
• ConnectionInterceptor: ConnectionInterceptor is the interface implemented by ConnectionManager "aspects". A ConnectionInterceptor implementation can provide one step of functionality for obtaining or releasing a ManagedConnection.
• MockWorkManager: Dummy implementation of WorkManager interface for use in BootstrapContextTest
• ActivationSpecWrapper: Wrapper for ActivationSpec instances. The framework assumes all RequiredConfigProperties are of type String, although it is unclear if this is required by the spec.
• LogXAResource: Works with JDBCLog to provide last resource optimization for a single 1-pc database. The database work is committed when the log writes its prepare record, not here.
• BootstrapContextTest: Unit tests for BootstrapContextImpl
• WorkExecutorPoolImpl: Based class for WorkExecutorPool. Sub-classes define the synchronization policy (should the call block until the end of the work; or when it starts et cetera).
• LocalXAResource: LocalXAResource adapts a local transaction to be controlled by a JTA transaction manager. Of course, it cannot provide xa semantics.
• AdminObjectWrapper: Wrapper around AdminObject that exposes its config-properties as GBeanAttributes and supplies a disconnectable proxy to bind in jndi.
• PooledWorkManagerTest: Timing is crucial for this test case, which focuses on the synchronization specificities of the doWork, startWork and scheduleWork.
• TimedOutPooledExecutor: PooledExecutor enforcing a timed out "blocked execution policy". The works submitted to this pooled executor MUST be a WorkWrapper.
• ConnectorMethodInterceptor: MethodInterceptor used by various Proxies. The important part of this class is the deserialization in the readResolve method.
• DefaultComponentInterceptor: Sample functionality for an interceptor that enables connection caching and obtaining connections outside a UserTransaction.
• GenericConnectionManager: GenericConnectionManager sets up a connection manager stack according to the policies described in the attributes.
• BootstrapContext: GBean BootstrapContext implementation that refers to externally configured WorkManager and XATerminator gbeans.
• BootstrapContextImpl: GBean BootstrapContext implementation that refers to externally configured WorkManager and XATerminator gbeans.
• ResourceAdapterWrapper: Dynamic GBean wrapper around a ResourceAdapter object, exposing the config-properties as GBean attributes.

Home | Contact Us | Privacy Policy | Terms of Service