You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "John Hawkins (JIRA)" <ax...@ws.apache.org> on 2005/02/22 14:58:48 UTC

[jira] Created: (AXISCPP-463) Server fault code fails with a serialise exception

Server fault code fails with a serialise exception
--------------------------------------------------

         Key: AXISCPP-463
         URL: http://issues.apache.org/jira/browse/AXISCPP-463
     Project: Axis-C++
        Type: Bug
  Components: Client - Engine  
    Reporter: John Hawkins


When we receive an unxpected fault from the server we fail with a deserialisin exception ->
Cannot deserialize the requested element. We shouldn't we should deserialise the exception and produce an appropriate exception.

The error was found when running  IHeaderBlockTest3 which produces a server fault code but returns back to the user the given exception.


-- 
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


[jira] Assigned: (AXISCPP-463) Server fault code fails with a serialise exception

Posted by "Mark Whitlock (JIRA)" <ax...@ws.apache.org>.
     [ http://issues.apache.org/jira/browse/AXISCPP-463?page=history ]

Mark Whitlock reassigned AXISCPP-463:
-------------------------------------

    Assign To: Mark Whitlock

> Server fault code fails with a serialise exception
> --------------------------------------------------
>
>          Key: AXISCPP-463
>          URL: http://issues.apache.org/jira/browse/AXISCPP-463
>      Project: Axis-C++
>         Type: Bug
>   Components: Client - Engine
>     Reporter: John Hawkins
>     Assignee: Mark Whitlock

>
> When we receive an unxpected fault from the server we fail with a deserialisin exception ->
> Cannot deserialize the requested element. We shouldn't we should deserialise the exception and produce an appropriate exception.
> The error was found when running  IHeaderBlockTest3 which produces a server fault code but returns back to the user the given exception.

-- 
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


[jira] Closed: (AXISCPP-463) Server fault code fails with a serialise exception

Posted by "Mark Whitlock (JIRA)" <ax...@ws.apache.org>.
     [ http://issues.apache.org/jira/browse/AXISCPP-463?page=history ]
     
Mark Whitlock closed AXISCPP-463:
---------------------------------

    Resolution: Fixed

I have fixed this issue by throwing back OtherFaultException which encapsulates all other faults which are generated by the server.

> Server fault code fails with a serialise exception
> --------------------------------------------------
>
>          Key: AXISCPP-463
>          URL: http://issues.apache.org/jira/browse/AXISCPP-463
>      Project: Axis-C++
>         Type: Bug
>   Components: Client - Engine
>     Reporter: John Hawkins
>     Assignee: Mark Whitlock

>
> When we receive an unxpected fault from the server we fail with a deserialisin exception ->
> Cannot deserialize the requested element. We shouldn't we should deserialise the exception and produce an appropriate exception.
> The error was found when running  IHeaderBlockTest3 which produces a server fault code but returns back to the user the given exception.

-- 
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