Beehive
  1. Beehive
  2. BEEHIVE-133

JSR-181 compliance: Exceptions not propagated correctly

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: V1Beta
    • Fix Version/s: V1Beta
    • Component/s: Web Services (181)
    • Labels:
      None

      Description

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

        Activity

        Hide
        Jeremiah Johnson added a comment -

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

        Show
        Jeremiah Johnson added a comment - This issue has mostly been resolved. There is one remaining issue that now has a more specific bug ( BEEHIVE-717 ).
        Hide
        Jongjin Choi added a comment -

        The patch is applied.

        Show
        Jongjin Choi added a comment - The patch is applied.
        Hide
        Jongjin Choi added a comment -

        I tested this case and found that there is no corresponding complexType for service specific exception is not generated in the WSDL.
        This prevents the Axis client stub to generate the service specific exception from the SOAP fault message.

        I patched the AxisHook.java, adding additional information for FaultDesc. The service specific exception is now propagated to Axis client.

        Show
        Jongjin Choi added a comment - I tested this case and found that there is no corresponding complexType for service specific exception is not generated in the WSDL. This prevents the Axis client stub to generate the service specific exception from the SOAP fault message. I patched the AxisHook.java, adding additional information for FaultDesc. The service specific exception is now propagated to Axis client.
        Hide
        Jongjin Choi added a comment -

        Axis' SOAP fault code does not follow WS-I BP now. But "soapenv:Server.generalException" fault code does not matter between Axis and Axis communication.
        (I think Axis should follow WS-I BP style for fault code.)

        But Axis' service specific exception implementation lacks of JAX-RPC 1.1 compatibility. This can be a cause for this issue.
        I wonder whether fault serialization (server-side) or fault deserialization (client-side) fails.

        Can you to upload a test case?

        Show
        Jongjin Choi added a comment - Axis' SOAP fault code does not follow WS-I BP now. But "soapenv:Server.generalException" fault code does not matter between Axis and Axis communication. (I think Axis should follow WS-I BP style for fault code.) But Axis' service specific exception implementation lacks of JAX-RPC 1.1 compatibility. This can be a cause for this issue. I wonder whether fault serialization (server-side) or fault deserialization (client-side) fails. Can you to upload a test case?

          People

          • Assignee:
            Jeremiah Johnson
            Reporter:
            Michael Merz
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development