You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@beehive.apache.org by "Jeremiah Johnson (JIRA)" <be...@incubator.apache.org> on 2005/05/13 02:28:05 UTC

[jira] Closed: (BEEHIVE-133) JSR-181 compliance: Exceptions not propagated correctly

     [ http://issues.apache.org/jira/browse/BEEHIVE-133?page=all ]
     
Jeremiah Johnson closed BEEHIVE-133:
------------------------------------

    Assign To: Jeremiah Johnson  (was: Jongjin Choi)

This issue has mostly been resolved.  There is one remaining issue that now has a more specific bug (BEEHIVE-717).

> JSR-181 compliance: Exceptions not propagated correctly
> -------------------------------------------------------
>
>          Key: BEEHIVE-133
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-133
>      Project: Beehive
>         Type: Bug
>   Components: Web Services (181)
>     Versions: V1Beta
>     Reporter: Michael Merz
>     Assignee: Jeremiah Johnson
>      Fix For: V1Beta

>
> User exceptions (subclasses of java.lang.Exception) are not properly propagated to the client. "soapenv:Server.generalException" show up on the client side instead.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira