[
https://issues.apache.org/jira/browse/OPENEJB-1091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025234#comment-13025234
]
Vamsavardhana Reddy commented on OPENEJB-1091:
----------------------------------------------
Further thoughts on the exception conversion...
There is no way that a cause can be packaged with a
javax.transaction.TransactionRolledbackException. The only option, if the
exception thrown in case of remote execution has to be a sub type of
java.rmi.RemoteException, is to use RemoteException itself.
> Cause of RollbackException swallowed
> ------------------------------------
>
> 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: Jean-Louis MONTEIRO
> Fix For: 3.0
>
> Attachments: OPENEJB-1091-convertException-new.patch,
> OPENEJB-1091-convertException.patch, open-ejb_1091.patch
>
>
> This is linked to OPENEJB-782 where the problem was first noted. The flaw
> described there still exists in 3.1, ie. the client still has no way of
> determining the reason a rollback occurred.
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
