You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by "Eric Covener (Created) (JIRA)" <ji...@apache.org> on 2012/02/23 21:56:48 UTC
[jira] [Created] (OWB-649) exceptions in EJB's are wrapped in
InvocationTargetException
exceptions in EJB's are wrapped in InvocationTargetException
------------------------------------------------------------
Key: OWB-649
URL: https://issues.apache.org/jira/browse/OWB-649
Project: OpenWebBeans
Issue Type: Bug
Components: Enterprise Web Beans
Affects Versions: 1.1.3
Reporter: Eric Covener
Assignee: Eric Covener
Fix For: 1.1.4
When an EJB is @Injected and the EjbBeanproxyHandler is used as the javassist MethodHandler, exceptions become wrapped in InvocationTargetException which a caller might not be prepared to inspect.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (OWB-649) exceptions in EJB's are wrapped in
InvocationTargetException
Posted by "Eric Covener (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OWB-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Covener resolved OWB-649.
------------------------------
Resolution: Fixed
> exceptions in EJB's are wrapped in InvocationTargetException
> ------------------------------------------------------------
>
> Key: OWB-649
> URL: https://issues.apache.org/jira/browse/OWB-649
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Enterprise Web Beans
> Affects Versions: 1.1.3
> Reporter: Eric Covener
> Assignee: Eric Covener
> Fix For: 1.1.4
>
> Original Estimate: 0.25h
> Remaining Estimate: 0.25h
>
> When an EJB is @Injected and the EjbBeanproxyHandler is used as the javassist MethodHandler, exceptions become wrapped in InvocationTargetException which a caller might not be prepared to inspect.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira