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

Quick Search    Search Deep

org.springframework.orm.hibernate.* (24)org.springframework.orm.hibernate3.* (25)
org.springframework.orm.ibatis.* (14)org.springframework.orm.jdo.* (19)
org.springframework.orm.ojb.* (12)

org.springframework.orm: Javadoc index of package org.springframework.orm.


Package Samples:

org.springframework.orm.ibatis.support: Package providing integration of iBATIS Database Layer with Spring concepts.  
org.springframework.orm.hibernate.support: Package providing integration of Hibernate 2.1 with Spring concepts.  
org.springframework.orm.hibernate3.support: Package providing integration of Hibernate3 with Spring concepts.  
org.springframework.orm.ojb.support: Package providing integration of Apache OJB with Spring concepts.  
org.springframework.orm.jdo.support: Package providing integration of JDO with Spring concepts.  
org.springframework.orm.ojb: Root package for Spring's O/R Mapping integration classes.  
org.springframework.orm.hibernate
org.springframework.orm.hibernate3
org.springframework.orm.ibatis
org.springframework.orm.jdo

Classes:

HibernateTransactionManager: PlatformTransactionManager implementation for a single Hibernate SessionFactory. Binds a Hibernate Session from the specified factory to the thread, potentially allowing for one thread Session per factory. SessionFactoryUtils and HibernateTemplate are aware of thread-bound Sessions and participate in such transactions automatically. Using either is required for Hibernate access code that needs to support this transaction handling mechanism. Supports custom isolation levels, and timeouts that get applied as appropriate Hibernate query timeouts. To support the latter, application code must either ...
HibernateTransactionManager: PlatformTransactionManager implementation for a single Hibernate SessionFactory. Binds a Hibernate Session from the specified factory to the thread, potentially allowing for one thread Session per factory. SessionFactoryUtils and HibernateTemplate are aware of thread-bound Sessions and participate in such transactions automatically. Using either is required for Hibernate access code that needs to support this transaction handling mechanism. Supports custom isolation levels, and timeouts that get applied as appropriate Hibernate query timeouts. To support the latter, application code must either ...
HibernateTemplate: Helper class that simplifies Hibernate data access code, and converts checked HibernateExceptions into unchecked DataAccessExceptions, following the org.springframework.dao exception hierarchy. Uses the same SQLExceptionTranslator mechanism as JdbcTemplate. Typically used to implement data access or business logic services that use Hibernate within their implementation but are Hibernate-agnostic in their interface. The latter or code calling the latter only have to deal with domain objects, query objects, and org.springframework.dao exceptions. The central method is "execute", supporting Hibernate ...
HibernateTemplate: Helper class that simplifies Hibernate data access code, and converts checked HibernateExceptions into unchecked DataAccessExceptions, following the org.springframework.dao exception hierarchy. Uses the same SQLExceptionTranslator mechanism as JdbcTemplate. Typically used to implement data access or business logic services that use Hibernate within their implementation but are Hibernate-agnostic in their interface. The latter or code calling the latter only have to deal with domain objects, query objects, and org.springframework.dao exceptions. The central method is "execute", supporting Hibernate ...
JdoTemplate: Helper class that simplifies JDO data access code, and converts JDOExceptions into Spring DataAccessExceptions, following the org.springframework.dao exception hierarchy. The central method is "execute", supporting JDO code implementing the JdoCallback interface. It provides JDO PersistenceManager handling such that neither the JdoCallback implementation nor the calling code needs to explicitly care about retrieving/closing PersistenceManagers, or handling JDO lifecycle exceptions. Typically used to implement data access or business logic services that use JDO within their implementation but are ...
LocalPersistenceManagerFactoryBean: FactoryBean that creates a local JDO PersistenceManager instance. Behaves like a PersistenceManagerFactory instance when used as bean reference, e.g. for JdoTemplate's "persistenceManagerFactory" property. Note that switching to a JndiObjectFactoryBean or a bean-style PersistenceManagerFactory instance is just a matter of configuration! The typical usage will be to register this as singleton factory (for a certain underlying data source) in an application context, and give bean references to application services that need it. Configuration settings can either be read from a properties file, specified ...
OpenSessionInViewFilter: Servlet 2.3 Filter that binds a Hibernate Session to the thread for the entire processing of the request. Intended for the "Open Session in View" pattern, i.e. to allow for lazy loading in web views despite the original transactions already being completed. This filter works similar to the AOP HibernateInterceptor: It just makes Hibernate Sessions available via the thread. It is suitable for non-transactional execution but also for middle tier transactions via HibernateTransactionManager or JtaTransactionManager. In the latter case, Sessions pre-bound by this filter will automatically be used for ...
OpenSessionInViewFilter: Servlet 2.3 Filter that binds a Hibernate Session to the thread for the entire processing of the request. Intended for the "Open Session in View" pattern, i.e. to allow for lazy loading in web views despite the original transactions already being completed. This filter works similar to the AOP HibernateInterceptor: It just makes Hibernate Sessions available via the thread. It is suitable for non-transactional execution but also for middle tier transactions via HibernateTransactionManager or JtaTransactionManager. In the latter case, Sessions pre-bound by this filter will automatically be used for ...
OpenSessionInViewInterceptor: Spring web HandlerInterceptor that binds a Hibernate Session to the thread for the entire processing of the request. Intended for the "Open Session in View" pattern, i.e. to allow for lazy loading in web views despite the original transactions already being completed. This interceptor works similar to the AOP HibernateInterceptor: It just makes Hibernate Sessions available via the thread. It is suitable for non-transactional execution but also for middle tier transactions via HibernateTransactionManager or JtaTransactionManager. In the latter case, Sessions pre-bound by this interceptor will automatically ...
OpenSessionInViewInterceptor: Spring web HandlerInterceptor that binds a Hibernate Session to the thread for the entire processing of the request. Intended for the "Open Session in View" pattern, i.e. to allow for lazy loading in web views despite the original transactions already being completed. This interceptor works similar to the AOP HibernateInterceptor: It just makes Hibernate Sessions available via the thread. It is suitable for non-transactional execution but also for middle tier transactions via HibernateTransactionManager or JtaTransactionManager. In the latter case, Sessions pre-bound by this interceptor will automatically ...
JdoTransactionManager: PlatformTransactionManager implementation for a single JDO PersistenceManagerFactory. Binds a JDO PersistenceManager from the specified factory to the thread, potentially allowing for one thread PersistenceManager per factory. PersistenceManagerFactoryUtils and JdoTemplate are aware of thread-bound persistence managers and participate in such transactions automatically. Using either is required for JDO access code supporting this transaction management mechanism. This implementation is appropriate for applications that solely use JDO for transactional data access. JTA (usually through JtaTransactionManager) ...
LocalSessionFactoryBean: FactoryBean that creates a local Hibernate SessionFactory instance. Behaves like a SessionFactory instance when used as bean reference, e.g. for HibernateTemplate's "sessionFactory" property. Note that switching to JndiObjectFactoryBean is just a matter of configuration! The typical usage will be to register this as singleton factory (for a certain underlying JDBC DataSource) in an application context, and give bean references to application services that need it. Configuration settings can either be read from a Hibernate XML file, specified as "configLocation", or completely via this class. A ...
JdoInterceptor: This interceptor binds a new JDO PersistenceManager to the thread before a method call, closing and removing it afterwards in case of any method outcome. If there already was a pre-bound PersistenceManager (e.g. from JdoTransactionManager, or from a surrounding JDO-intercepted method), the interceptor simply takes part in it. Application code must retrieve a JDO PersistenceManager via PersistenceManagerFactoryUtils' getPersistenceManager method, to be able to detect a thread-bound PersistenceManager. It is preferable to use getPersistenceManager with allowCreate=false, as the code relies on the ...
LocalSessionFactoryBean: FactoryBean that creates a local Hibernate SessionFactory instance. Behaves like a SessionFactory instance when used as bean reference, e.g. for HibernateTemplate's "sessionFactory" property. Note that switching to JndiObjectFactoryBean is just a matter of configuration! The typical usage will be to register this as singleton factory (for a certain underlying JDBC DataSource) in an application context, and give bean references to application services that need it. Configuration settings can either be read from a Hibernate XML file, specified as "configLocation", or completely via this class. A ...
HibernateInterceptor: This interceptor binds a new Hibernate Session to the thread before a method call, closing and removing it afterwards in case of any method outcome. If there already was a pre-bound Session (e.g. from HibernateTransactionManager, or from a surrounding Hibernate-intercepted method), the interceptor simply takes part in it. Application code must retrieve a Hibernate Session via SessionFactoryUtils' getSession method, to be able to detect a thread-bound Session. It is preferable to use getSession with allowCreate=false, as the code relies on the interceptor to provide proper Session handling. Typically ...
HibernateInterceptor: This interceptor binds a new Hibernate Session to the thread before a method call, closing and removing it afterwards in case of any method outcome. If there already was a pre-bound Session (e.g. from HibernateTransactionManager, or from a surrounding Hibernate-intercepted method), the interceptor simply takes part in it. Application code must retrieve a Hibernate Session via SessionFactoryUtils' getSession method, to be able to detect a thread-bound Session. It is preferable to use getSession with allowCreate=false, as the code relies on the interceptor to provide proper Session handling. Typically ...
SqlMapClientTemplate: Helper class that simplifies data access via the SqlMapClient API of iBATIS SQL Maps, and converts checked SQLExceptions into unchecked DataAccessExceptions, following the org.springframework.dao exception hierarchy. Uses the same SQLExceptionTranslator mechanism as JdbcTemplate. The main method of this class executes a callback that implements a data access action. Furthermore, this class provides numerous convenience methods that mirror SqlMapExecutor's execution methods. See the SqlMapExecutor javadocs for details on those methods. It is generally recommended to use the convenience methods on ...
PersistenceBrokerTemplate: Helper class that simplifies OJB PersistenceBroker data access code, and converts PersistenceBrokerExceptions into Spring DataAccessExceptions, following the org.springframework.dao exception hierarchy. The central method is "execute", supporting OJB code implementing the PersistenceBrokerCallback interface. It provides PersistenceBroker handling such that neither the PersistenceBrokerCallback implementation nor the calling code needs to explicitly care about retrieving/closing PersistenceBrokers, or handling OJB lifecycle exceptions. Typically used to implement data access or business logic services ...
TransactionAwareDataSourceConnectionFactory: Subclass of LocalDataSourceConnectionFactory that returns transaction-aware proxies for all DataSources retrieved by OJB. Define the following entry in your OJB.properties to use this connection factory: ConnectionFactoryClass=org.springframework.orm.ojb.support.TransactionAwareDataSourceConnectionFactory This connection factory allows Spring's OJB access to participate in JDBC-based transactions managed outside of OJB (for example, by Spring's DataSourceTransactionManager). This can be convenient if you need a different local transaction strategy for another O/R mapping tool, for example, but ...
FilterDefinitionFactoryBean: Convenient FactoryBean for defining Hibernate FilterDefinitions. Exposes a corresponding Hibernate FilterDefinition object. Typically defined as inner bean within a LocalSessionFactoryBean definition, as list element for the "filterDefinitions" bean property. For example: <bean id="sessionFactory" class="org.springframework.orm.hibernate3.LocalSessionFactoryBean"> ... <property name="filterDefinitions"> <list> <bean class="org.springframework.orm.hibernate3.FilterDefinitionFactoryBean"> <property name="filterName"><value>myFilter</value></property> ...
OpenPersistenceManagerInViewFilter: Servlet 2.3 Filter that binds a JDO PersistenceManager to the thread for the entire processing of the request. Intended for the "Open PersistenceManager in View" pattern, i.e. to allow for lazy loading in web views despite the original transactions already being completed. This filter works similar to the AOP JdoInterceptor: It just makes JDO PersistenceManagers available via the thread. It is suitable for non-transactional execution but also for middle tier transactions via JdoTransactionManager or JtaTransactionManager. In the latter case, PersistenceManagers pre-bound by this filter will automatically ...
HibernateOperations: Interface that specifies a basic set of Hibernate operations. Implemented by HibernateTemplate. Not often used, but a useful option to enhance testability, as it can easily be mocked or stubbed. Provides HibernateTemplate's data access methods that mirror various Session methods. See the Hibernate Session javadocs for details on those methods. Note that operations that return an Iterator (i.e. iterate ) are supposed to be used within Spring-driven or JTA-driven transactions (with HibernateTransactionManager, JtaTransactionManager, or EJB CMT). Else, the Iterator won't be able to read results from ...
HibernateOperations: Interface that specifies a basic set of Hibernate operations. Implemented by HibernateTemplate. Not often used, but a useful option to enhance testability, as it can easily be mocked or stubbed. Provides HibernateTemplate's data access methods that mirror various Session methods. See the Hibernate Session javadocs for details on those methods. Note that operations that return an Iterator (i.e. iterate ) are supposed to be used within Spring-driven or JTA-driven transactions (with HibernateTransactionManager, JtaTransactionManager, or EJB CMT). Else, the Iterator won't be able to read results from ...
LocalDataSourceConnectionFactory: OJB connection factory that delegates to Spring-managed DataSource beans. Define the following entry in your OJB.properties to use this connection factory: ConnectionFactoryClass=org.springframework.orm.ojb.support.LocalDataSourceConnectionFactory Interprets JCD aliases in OJB's JDBC connection descriptors as Spring bean names. For example, the following will delegate to the Spring bean named "myDataSource": <jdbc-connection-descriptor jcd-alias="myDataSource" default-connection="true" useAutoCommit="1"/> Depends on LocalOjbConfigurer being defined as Spring bean, which will expose the Spring ...
JdoCallback: Callback interface for JDO code. To be used with JdoTemplate's execute method, assumably often as anonymous classes within a method implementation. The typical implementation will call PersistenceManager CRUD to perform some operations on persistent objects. Note that JDO works on bytecode-modified Java objects, to be able to perform dirty detection on each modification of a persistent instance field. In contrast to Hibernate, using returned objects outside of an active PersistenceManager poses a problem: To be able to read and modify fields e.g. in a web GUI, one has to explicitly make the instances ...

Home | Contact Us | Privacy Policy | Terms of Service