Mailing-List: contact user-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Users Mailing List" <user@struts.apache.org>
Received-SPF: pass (athena.apache.org: domain of burtonrhodes@gmail.com
 designates 216.239.58.188 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:mime-version:content-type
         :content-transfer-encoding:content-disposition;
        b=kAX1A+K/Htx01uqqVegdOgFSG1AzIULWiDXq3erkw928lV8TrKqJCeXVAvdm/Rk6a/
         7RGuceSnQzo0+Qlcn7HMh6grt6Lcr38zhpr+cMX0byAngkCmEERQro4CtOgnnCPil96n
         FzEEHXLTgc0C4egHLCe9ImP0Kf47dbC93U5Mo=
Message-ID: <3017fd9e0811131231g5c885644ke8911fcb1614943e@mail.gmail.com>
Date: Thu, 13 Nov 2008 14:31:17 -0600
From: "Burton Rhodes" <burtonrhodes@gmail.com>
To: "Struts Users Mailing List" <user@struts.apache.org>
Subject: Using validation with Hibernate...
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I am having trouble getting Struts 2.x to implement validation and
hibernate using the HibernateSessionRequestFilter (the pattern
suggested on Hibernate.org).  When the validation fails, Hibernate
will still update the object in the database when the HibernateFilter
closes the transaction.  I get why this is happening, but I can't seem
to find anyone who has really figured out an *elegant* solution.  Any
ideas?


public class HibernateSessionRequestFilter implements Filter {

   static Logger log = Logger.getLogger(HibernateSessionRequestFilter.class);

   private SessionFactory sf;

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

        try {

        	// This starts the Hibernate transaction
            sf.getCurrentSession().beginTransaction();

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

            // Commit and cleanup
            sf.getCurrentSession().getTransaction().commit();  <----
********* Data is written here no matter what ************

        } catch (StaleObjectStateException staleEx) {
            log.fatal("This interceptor does not implement optimistic
concurrency control!");
            log.fatal("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;

        }
        // This is a catch-all catch, define other Exceptions here
        catch (Throwable ex) {
            // Rollback only
            ex.printStackTrace();
            try {
                if (sf.getCurrentSession().getTransaction().isActive()) {
                	log.fatal("Trying to rollback database transaction
after exception");
                    sf.getCurrentSession().getTransaction().rollback();
                }
            } catch (Throwable rbEx) {
            	log.fatal("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.trace("Initializing filter...");
    	log.trace("Obtaining SessionFactory from static HibernateUtil
singleton...");
        sf = HibernateUtil.getSessionFactory();
    }

    public void destroy() {}

}

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org