You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Jacek Laskowski (JIRA)" <ji...@apache.org> on 2009/06/12 13:05:07 UTC
[jira] Updated: (OPENEJB-980) @ApplicationException inheritance
[ https://issues.apache.org/jira/browse/OPENEJB-980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jacek Laskowski updated OPENEJB-980:
------------------------------------
Summary: @ApplicationException inheritance (was: Optional @ApplicationException inheritance)
> @ApplicationException inheritance
> ---------------------------------
>
> Key: OPENEJB-980
> URL: https://issues.apache.org/jira/browse/OPENEJB-980
> Project: OpenEJB
> Issue Type: New Feature
> Reporter: Geoff Callender
> Assignee: Jacek Laskowski
> Fix For: 3.1.x
>
>
> When @ApplicationException(rollback = true) is annotated on an exception thrown by a session bean then all is well - the client receives the exception.
> But if the annotation is moved up to a superclass of the exception then all is not well - the client receives EJBTransactionRolledbackException.
> In the app server I am porting from the following worked OK, and I believe it is the correct behaviour:
> public interface DogServiceRemote {
> void createDog(Dog dog) throws BusinessException;
> }
> @ApplicationException(rollback = true)
> abstract public class BusinessException extends Exception {
> ...
> }
> public class ValueRequiredException extends BusinessException {
> ...
> }
> where createDog(...) throws many different subclasses of BusinessException, none of which is annotated with @ApplicationException.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.