axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (AXIS-1577) EJBProvider doesn't handle java.rmi.ServerException
Date Thu, 14 Oct 2004 22:29:51 GMT
The following comment has been added to this issue:

     Author: David Green
    Created: Thu, 14 Oct 2004 3:29 PM
:) No... not tested.  The previous version was tested over 1.4.  Would you like me to test/verify
the suggested fix?  
View this comment:

View the issue:

Here is an overview of the issue:
        Key: AXIS-1577
    Summary: EJBProvider doesn't handle java.rmi.ServerException
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Axis
             Basic Architecture
             current (nightly)

   Reporter: David Green

    Created: Tue, 28 Sep 2004 12:53 PM
    Updated: Thu, 14 Oct 2004 3:29 PM
Environment: All OS, J2EE 1.3 (JBoss 3.2.3) using JDK 1.4.2_05

java.rmi.ServerException is thrown when a RuntimeException is thrown.  Since the original
exception is wrapped in a ServerException, the SOAP fault is not created properly.

The EJBProvider should override invokeMethod as follows:

protected Object invokeMethod(MessageContext msgContext, Method method, Object obj, Object[]
argValues) throws Exception {
        try {
            return super.invokeMethod(msgContext, method, obj, argValues);
        } catch (ServerException serverException) {
            throw (RuntimeException) serverException.getCause();

This will ensure that the original exception is handled properly according to the type mappings.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message