You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tomee.apache.org by "Geoff Callender (JIRA)" <ji...@apache.org> on 2009/10/20 13:57:59 UTC

[jira] Updated: (OPENEJB-1091) CLONE -RollbackException swallowed in TransactionPolicy

     [ https://issues.apache.org/jira/browse/OPENEJB-1091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Geoff Callender updated OPENEJB-1091:
-------------------------------------

    Description: 
I can't reopen OPENEJB-782 so I've cloned it.  The flaw described there still exists in 3.1. The client still has no way of determining the cause of the exception.

When the client digs into the exception cause all it finds is javax.transaction.RollbackException. The originating javax.persistence.PersistenceException or java.sql.SQLException is missing.

  was:
See https://issues.apache.org/jira/browse/GERONIMO-3907 where a user discovered the problem

Looks like EJB 3 core spec 14.3.10 says we should be throwing an EJBException or maybe RemoteException here.


> CLONE -RollbackException swallowed in TransactionPolicy
> -------------------------------------------------------
>
>                 Key: OPENEJB-1091
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-1091
>             Project: OpenEJB
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 3.0-beta-2
>            Reporter: Geoff Callender
>            Assignee: David Jencks
>             Fix For: 3.0
>
>
> I can't reopen OPENEJB-782 so I've cloned it.  The flaw described there still exists in 3.1. The client still has no way of determining the cause of the exception.
> When the client digs into the exception cause all it finds is javax.transaction.RollbackException. The originating javax.persistence.PersistenceException or java.sql.SQLException is missing.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.