[
https://issues.apache.org/jira/browse/OPENEJB-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks closed OPENEJB-1195.
---------------------------------
Fix Version/s: 3.2
Resolution: Fixed
rev 983147.
OPENEJB-980 implemented some inheritance support where subclasses are always
the same kind of app exception unless re-described in an annotation or xml.
This solution attempted to calculate all exceptions at deployment time.
However it had several problems. One is that it didn't merge xml and
annotations. A more serous problem is that it didn't deal with inheritance of
exceptions described in xml.
While deploy-time calculation of all app exceptions and their type would result
in faster runtime performance, it would also require an api change in
xbean-finder to add a method to find all subclasses of a given class. I have
opted for runtime calculation of exception type.
The current code just tracks the rollback and inherited flags on application
exceptions that are explicitly mentioned in xml or annotations. At runtime we
examine superclasses of an exception until we find one that we know about to
determine whether it's an app exception, and its rollback status.
> javax.ejb.ApplicationException inherited()
> ------------------------------------------
>
> Key: OPENEJB-1195
> URL: https://issues.apache.org/jira/browse/OPENEJB-1195
> Project: OpenEJB
> Issue Type: Sub-task
> Components: ejb31
> Reporter: David Blevins
> Assignee: David Jencks
> Fix For: 3.2
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
