ws-soap-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Assigned: (SOAP-165) Exceptions from deserializer not sent by faultListener
Date Wed, 17 Mar 2004 15:29:16 GMT

   The following issue has been re-assigned.

   Assignee: Scott Nichol (
View the issue:

Here is an overview of the issue:
        Key: SOAP-165
    Summary: Exceptions from deserializer not sent by faultListener
       Type: Improvement

     Status: Open
   Priority: Minor

    Project: Apache SOAP

   Assignee: Scott Nichol
   Reporter: Christian Landbo

    Created: Wed, 17 Mar 2004 3:33 AM
    Updated: Wed, 17 Mar 2004 7:29 AM

Any exceptions thrown from a deserializer won't get sent to a custom faultListener since the
'DeploymentDescriptor dd' is null at that point in the RPCRouterServlet.

Scott Nichol:
I believe you are correct. I find it understandable that the code works this way, although
it does not really have to.

In order to determine the correct deployment descriptor, Apache SOAP must parse the namespace
from the XML element specifying the
method.  It does this within RPCRouter#extractCallFromEnvelope.  Interestingly, within that
method, after getting the namespace,
Apache SOAP gets the deployment descriptor to verify that the namespace is supported.  When
the method returns,
RPCRouterServlet#doPost gets its own copy of the deployment descriptor.  So, if the RPCRouterServlet
could have RPCRouter set its
deployment descriptor reference, it would give you the desired behavior.

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