[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openejb-user
Subject:    Re: Exception in Transaction does not show the original Cause
From:       David Blevins <david.blevins () visi ! com>
Date:       2008-12-29 2:48:01
Message-ID: 17427339-5297-4DE6-BEED-7A07580F0DCA () visi ! com
[Download RAW message or body]


On Dec 22, 2008, at 12:34 AM, Maxime Thieu wrote:

>
> Hello,
>
> I am using OpenEJB3.1 in Tomcat with JPA and Hibernate 3.3 as  
> provider.
>
> It works well, but when an persistence exception occurs (originaly  
> thrown by
> Hibernate, for exemple, Constraint violation), the visible Exception  
> is :
> javax.ejb.EJBTransactionRolledbackException: Transaction was rolled  
> back,
> presumably because setRollbackOnly was called during a synchronization
>
> With no indication of the Hibernate Exception (whereas with Spring
> framework, the original Hibernate cause is visible)
>
> Is there any way to configure the Transaction Manager to have the  
> original
> cause (Hibernate Exception) in logs ?

Hi Maxime,

This response would intended for you as well:

  http://www.nabble.com/Catching-OpenJPA-validation-exceptions-in-OpenEJB-to21146938.html

You Geoff and Luis make three requests in the last week for this.   
We'll definitely have to figure something out here.

-David

[prev in list] [next in list] [prev in thread] [next in thread]