类 AbstractSessionFactoryBean

字段详细资料

• logger

  protected final Log logger

  已过时。
  Logger available to subclasses

构造器详细资料

• AbstractSessionFactoryBean

  public AbstractSessionFactoryBean()

  已过时。

方法详细资料

• setDataSource

  public void setDataSource​(DataSource dataSource)

  已过时。
  Set the DataSource to be used by the SessionFactory. If set, this will override corresponding settings in Hibernate properties.

  If this is set, the Hibernate settings should not define a connection provider to avoid meaningless double configuration.

  If using HibernateTransactionManager as transaction strategy, consider proxying your target DataSource with a LazyConnectionDataSourceProxy. This defers fetching of an actual JDBC Connection until the first JDBC Statement gets executed, even within JDBC transactions (as performed by HibernateTransactionManager). Such lazy fetching is particularly beneficial for read-only operations, in particular if the chances of resolving the result in the second-level cache are high.

  As JTA and transactional JNDI DataSources already provide lazy enlistment of JDBC Connections, LazyConnectionDataSourceProxy does not add value with JTA (i.e. Spring's JtaTransactionManager) as transaction strategy.

  另请参阅:

  setUseTransactionAwareDataSource(boolean), HibernateTransactionManager, JtaTransactionManager, LazyConnectionDataSourceProxy

• getDataSource

  public DataSource getDataSource()

  已过时。
  Return the DataSource to be used by the SessionFactory.

• setUseTransactionAwareDataSource

  public void setUseTransactionAwareDataSource​(boolean useTransactionAwareDataSource)

  已过时。
  Set whether to use a transaction-aware DataSource for the SessionFactory, i.e. whether to automatically wrap the passed-in DataSource with Spring's TransactionAwareDataSourceProxy.

  Default is "false": LocalSessionFactoryBean is usually used with Spring's HibernateTransactionManager or JtaTransactionManager, both of which work nicely on a plain JDBC DataSource. Hibernate Sessions and their JDBC Connections are fully managed by the Hibernate/JTA transaction infrastructure in such a scenario.

  If you switch this flag to "true", Spring's Hibernate access will be able to participate in JDBC-based transactions managed outside of Hibernate (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 still want Hibernate access to join into those transactions.

  A further benefit of this option is that plain Sessions opened directly via the SessionFactory, outside of Spring's Hibernate support, will still participate in active Spring-managed transactions. However, consider using Hibernate's getCurrentSession() method instead (see javadoc of "exposeTransactionAwareSessionFactory" property).

  WARNING: When using a transaction-aware JDBC DataSource in combination with OpenSessionInViewFilter/Interceptor, whether participating in JTA or external JDBC-based transactions, it is strongly recommended to set Hibernate's Connection release mode to "after_transaction" or "after_statement", which guarantees proper Connection handling in such a scenario. In contrast to that, HibernateTransactionManager generally requires release mode "on_close".

  Note: If you want to use Hibernate's Connection release mode "after_statement" with a DataSource specified on this LocalSessionFactoryBean (for example, a JTA-aware DataSource fetched from JNDI), switch this setting to "true". Otherwise, the ConnectionProvider used underneath will vote against aggressive release and thus silently switch to release mode "after_transaction".

  另请参阅:

  setDataSource(javax.sql.DataSource), setExposeTransactionAwareSessionFactory(boolean), TransactionAwareDataSourceProxy, DataSourceTransactionManager, OpenSessionInViewFilter, OpenSessionInViewInterceptor, HibernateTransactionManager, JtaTransactionManager

• isUseTransactionAwareDataSource

  protected boolean isUseTransactionAwareDataSource()

  已过时。
  Return whether to use a transaction-aware DataSource for the SessionFactory.

• setExposeTransactionAwareSessionFactory

  public void setExposeTransactionAwareSessionFactory​(boolean exposeTransactionAwareSessionFactory)

  已过时。
  Set whether to expose a transaction-aware current Session from the SessionFactory's getCurrentSession() method, returning the Session that's associated with the current Spring-managed transaction, if any.

  Default is "true", letting data access code work with the plain Hibernate SessionFactory and its getCurrentSession() method, while still being able to participate in current Spring-managed transactions: with any transaction management strategy, either local or JTA / EJB CMT, and any transaction synchronization mechanism, either Spring or JTA. Furthermore, getCurrentSession() will also seamlessly work with a request-scoped Session managed by OpenSessionInViewFilter/Interceptor.

  Turn this flag off to expose the plain Hibernate SessionFactory with Hibernate's default getCurrentSession() behavior, supporting plain JTA synchronization only. Alternatively, simply override the corresponding Hibernate property "hibernate.current_session_context_class".

  另请参阅:

  SpringSessionContext, SessionFactory.getCurrentSession(), JtaTransactionManager, HibernateTransactionManager, OpenSessionInViewFilter, OpenSessionInViewInterceptor

• isExposeTransactionAwareSessionFactory

  protected boolean isExposeTransactionAwareSessionFactory()

  已过时。
  Return whether to expose a transaction-aware proxy for the SessionFactory.

• afterPropertiesSet

  public void afterPropertiesSet()
                          throws Exception

  已过时。
  Build and expose the SessionFactory.

  指定者:

  afterPropertiesSet 在接口中 InitializingBean

  抛出:

  Exception - in the event of misconfiguration (such as failure to set an essential property) or if initialization fails for any other reason

  另请参阅:

  buildSessionFactory(), wrapSessionFactoryIfNecessary(org.hibernate.SessionFactory)

• wrapSessionFactoryIfNecessary

  protected SessionFactory wrapSessionFactoryIfNecessary​(SessionFactory rawSf)

  已过时。
  Wrap the given SessionFactory with a proxy, if demanded.

  The default implementation simply returns the given SessionFactory as-is. Subclasses may override this to implement transaction awareness through a SessionFactory proxy, for example.

  参数:

  rawSf - the raw SessionFactory as built by buildSessionFactory()

  返回:

  the SessionFactory reference to expose

  另请参阅:

  buildSessionFactory()

• getSessionFactory

  protected final SessionFactory getSessionFactory()

  已过时。
  Return the exposed SessionFactory. Will throw an exception if not initialized yet.

  返回:

  the SessionFactory (never null)

  抛出:

  IllegalStateException - if the SessionFactory has not been initialized yet

• destroy

  public void destroy()
               throws HibernateException

  已过时。
  Close the SessionFactory on bean factory shutdown.

  指定者:

  destroy 在接口中 DisposableBean

  抛出:

  HibernateException

• getObject

  public SessionFactory getObject()

  已过时。
  Return the singleton SessionFactory.

  指定者:

  getObject 在接口中 FactoryBean<SessionFactory>

  返回:

  an instance of the bean (can be null)

  另请参阅:

  FactoryBeanNotInitializedException

• getObjectType

  public Class<? extends SessionFactory> getObjectType()

  已过时。
  从接口复制的说明: FactoryBean
  Return the type of object that this FactoryBean creates, or null if not known in advance.

  This allows one to check for specific types of beans without instantiating objects, for example on autowiring.

  In the case of implementations that are creating a singleton object, this method should try to avoid singleton creation as far as possible; it should rather estimate the type in advance. For prototypes, returning a meaningful type here is advisable too.

  This method can be called before this FactoryBean has been fully initialized. It must not rely on state created during initialization; of course, it can still use such state if available.

  NOTE: Autowiring will simply ignore FactoryBeans that return null here. Therefore it is highly recommended to implement this method properly, using the current state of the FactoryBean.

  指定者:

  getObjectType 在接口中 FactoryBean<SessionFactory>

  返回:

  the type of object that this FactoryBean creates, or null if not known at the time of the call

  另请参阅:

  ListableBeanFactory.getBeansOfType(java.lang.Class<T>)

• isSingleton

  public boolean isSingleton()

  已过时。
  从接口复制的说明: FactoryBean
  Is the object managed by this factory a singleton? That is, will FactoryBean.getObject() always return the same object (a reference that can be cached)?

  NOTE: If a FactoryBean indicates to hold a singleton object, the object returned from getObject() might get cached by the owning BeanFactory. Hence, do not return true unless the FactoryBean always exposes the same reference.

  The singleton status of the FactoryBean itself will generally be provided by the owning BeanFactory; usually, it has to be defined as singleton there.

  NOTE: This method returning false does not necessarily indicate that returned objects are independent instances. An implementation of the extended SmartFactoryBean interface may explicitly indicate independent instances through its SmartFactoryBean.isPrototype() method. Plain FactoryBean implementations which do not implement this extended interface are simply assumed to always return independent instances if the isSingleton() implementation returns false.

  指定者:

  isSingleton 在接口中 FactoryBean<SessionFactory>

  返回:

  whether the exposed object is a singleton

  另请参阅:

  FactoryBean.getObject(), SmartFactoryBean.isPrototype()

• buildSessionFactory

  protected abstract SessionFactory buildSessionFactory()
                                                 throws Exception

  已过时。
  Build the underlying Hibernate SessionFactory.

  返回:

  the raw SessionFactory (potentially to be wrapped with a transaction-aware proxy before it is exposed to the application)

  抛出:

  Exception - in case of initialization failure

• afterSessionFactoryCreation

  protected void afterSessionFactoryCreation()
                                      throws Exception

  已过时。
  Hook that allows post-processing after the SessionFactory has been successfully created. The SessionFactory is already available through getSessionFactory() at this point.

  This implementation is empty.

  抛出:

  Exception - in case of initialization failure

  另请参阅:

  getSessionFactory()

• beforeSessionFactoryDestruction

  protected void beforeSessionFactoryDestruction()

  已过时。
  Hook that allows shutdown processing before the SessionFactory will be closed. The SessionFactory is still available through getSessionFactory() at this point.

  This implementation is empty.

  另请参阅:

  getSessionFactory()