-
1. Re: Invocation exception handling
thomas.diesler Aug 14, 2007 5:15 AM (in response to palin)How about moving
if (th instanceof InvocationTargetException) { // Unwrap the throwable raised by the service endpoint implementation Throwable targetEx = ((InvocationTargetException)th).getTargetException(); handleInvocationException(targetEx); }
to native and only unwrap the MBeanException as part of the SPI.
Currently, the InvocationHandler = f(container). It'll be difficult ot make it f(container,stack) -
2. Re: Invocation exception handling
thomas.diesler Aug 14, 2007 6:25 AM (in response to palin)I've done the above. Maybe you could have a look if this fixes the Metro issue
-
3. Re: Invocation exception handling
palin Aug 14, 2007 11:00 AM (in response to palin)"thomas.diesler@jboss.com" wrote:
I've done the above. Maybe you could have a look if this fixes the Metro issue
Yes, I did some tests and it fixes the Metro issues, thus I've just removed the "FIXME" in the framework jaxws/exception test.
Thank you -
4. Re: Invocation exception handling
yhrn Mar 28, 2008 12:28 PM (in response to palin)Hi,
I still have this behaviour. My environement is JBoss AS 4.2.2. with jbossws-3.0-metro-1.0.0.GA.
All wsdl fault exceptions that are thrown by my EJB3 web service implementation are wrapped in a WebServiceException in org.jboss.wsf.stack.sunri.InvokerEJB3.handleException (line 117). Hence, a JAX-WS client receives a SoapFaultException with a WebServiceException as cause that in turn has the "real" exception as cause.
I've tried web services generated from WSDL and also simple examples where I manually annotated java classes.
This is a showstopper for us, so please help.
Regards, Mattias -
5. Re: Invocation exception handling
asoldano Mar 28, 2008 12:51 PM (in response to palin)Could you please create a new jira issue and attach a simple test case showing what you said? The current implementation of the exception handling with the metro stack is tested through the framework testsuite (see org.jboss.test.ws.jaxws.samples.exception.ExceptionTestCase). May be the exception your enpoint raises is not declared as a fault in the contract?
-
6. Re: Invocation exception handling
yhrn Mar 31, 2008 5:38 AM (in response to palin)Ok,
I have created a new JIRA http://jira.jboss.com/jira/browse/JBWS-2087 -
7. Re: Invocation exception handling
nhe Apr 10, 2008 6:57 AM (in response to palin)Hi,
I have, as a workaround, in InvokerEJB3.handleException wrapped checked exceptions into InvocationTargetExceptions.
Maybe a solution would be to change the InvocationHandler to first unwrap the MBeanException and then wrap it into a InvocationTargetException.
/Niklas