Question

最近我做了一些工作来检查，在我们的应用程序中将会话相关代码放在哪里， ie。获取当前会话（sessionFactory.getCurrentSession（））;

我已经在应用程序中看到过两次这样的代码，一个在 HibernateSessionRequestFileter类

package com.persistence;

import java.io.IOException;

import javax.servlet.Filter;
import javax.servlet.FilterChain;
import javax.servlet.FilterConfig;
import javax.servlet.ServletException;
import javax.servlet.ServletRequest;
import javax.servlet.ServletResponse;

import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
import org.hibernate.SessionFactory;
import org.hibernate.StaleObjectStateException;
public class HibernateSessionRequestFilter implements Filter {

    private static Log log = LogFactory.getLog(HibernateSessionRequestFilter.class);

    private SessionFactory sf;

    public void doFilter(ServletRequest request,
                         ServletResponse response,
                         FilterChain chain)
            throws IOException, ServletException {

        try {
            log.debug("Starting a database transaction");
            sf.getCurrentSession().beginTransaction();

            // Call the next filter (continue request processing)
            chain.doFilter(request, response);

            // Commit and cleanup
            log.debug("Committing the database transaction");
            sf.getCurrentSession().getTransaction().commit();

        } catch (StaleObjectStateException staleEx) {
            log.error("This interceptor does not implement optimistic concurrency control!");
            log.error("Your application will not work until you add compensation actions!");
            // Rollback, close everything, possibly compensate for any permanent changes
            // during the conversation, and finally restart business conversation. Maybe
            // give the user of the application a chance to merge some of his work with
            // fresh data... what you do here depends on your applications design.
            throw staleEx;
        } catch (Throwable ex) {
            // Rollback only
            ex.printStackTrace();
            try {
                if (sf.getCurrentSession().getTransaction().isActive()) {
                    log.debug("Trying to rollback database transaction after exception");
                    //sf.getCurrentSession().getTransaction().rollback();
                }
            } catch (Throwable rbEx) {
                log.error("Could not rollback transaction after exception!", rbEx);
            }

            // Let others handle it... maybe another interceptor for exceptions?
            throw new ServletException(ex);
        }
    }

    public void init(FilterConfig filterConfig) throws ServletException {
        log.debug("Initializing filter...");
        log.debug("Obtaining SessionFactory from static HibernateUtil singleton");
        sf = HibernateUtil.getSessionFactory();
    }

    public void destroy() {}


}

GenericHibernateDAO类中的另一个如下所示，

protected Session getSession() {

        if (session == null) {
            session = HibernateUtil.getSessionFactory().getCurrentSession();
        } else if (!session.isConnected()) {
            session = HibernateUtil.getSessionFactory().getCurrentSession();
        }
        return session;
    }

任何人都可以帮助我理解，为什么我们必须在两个地方获得现状？当我们开始交易时，我们正在获得当前的热情，就像我们坚持或从数据库中获取对象一样，我们再次获得当前的热情，为什么会这样？

Answer 1

这看起来像OpenSessionInView模式的版本，其中Hibernate会话在收到请求时打开，并在呈现响应后关闭。

在过滤器中打开一个会话并启动一个事务。

然后处理请求，并且在Dao中，对getCurrentSession()的调用只获得当前打开的会话，而不是创建新的会话。

dao完成了它的工作。然后过滤器提交事务并关闭会话。

为什么我们在应用程序中获得两次currentsession？

1 个答案: