[esb-issues] [JBoss JIRA] Updated: (JBESB-647) JAXRRegistryService doesn't unpack "cause" exception after proxied invocation of Registry
Tom Fennelly (JIRA)
jira-events at lists.jboss.org
Tue Jun 26 05:29:16 EDT 2007
[ http://jira.jboss.com/jira/browse/JBESB-647?page=all ]
Tom Fennelly updated JBESB-647:
-------------------------------
Component/s: Registry and Repository
> JAXRRegistryService doesn't unpack "cause" exception after proxied invocation of Registry
> -----------------------------------------------------------------------------------------
>
> Key: JBESB-647
> URL: http://jira.jboss.com/jira/browse/JBESB-647
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Registry and Repository
> Affects Versions: 4.2 Milestone Release 2
> Reporter: Tom Fennelly
> Assigned To: Mark Little
> Fix For: 4.2
>
>
> The JAXRRegistryService class creates a dynamic proxy around the Registry implementation class. It does this so as to push and pop the scoped classloader.
> As a proxy, it obviously makes reflective "invoke" calls on the proxied Registry instance. If there's an exception, it comes back as a cause on an InvocationTargetException, causing an UndeclaredThrowableException wherever Regsitry methods are being called. This obscures the resulting exceptions that are appearing in the console/logs.
> The dynamic proxy in JAXRRegistryService should catch all InvocationTargetException, extract and rethrow its cause (which is the real exception that's declared on the Registry interface).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the esb-issues
mailing list