You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by ax...@ws.apache.org on 2004/10/14 22:53:53 UTC

[jira] Commented: (AXIS-1577) EJBProvider doesn't handle java.rmi.ServerException

The following comment has been added to this issue:

     Author: Davanum Srinivas
    Created: Thu, 14 Oct 2004 1:52 PM
       Body:
David,

getCause does not work in JDK1.3...Any workarounds?

thanks,
dims
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/AXIS-1577?page=comments#action_54100

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXIS-1577

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
 Components: 
             Basic Architecture
   Versions:
             current (nightly)

   Assignee: 
   Reporter: David Green

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

Description:
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.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira