axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davanum Srinivas (JIRA)" <>
Subject [jira] Updated: (AXIS-1845) SOAP response returned in 202 error code
Date Fri, 28 Sep 2007 12:54:13 GMT


Davanum Srinivas updated AXIS-1845:

    Assignee:     (was: Davanum Srinivas)

> SOAP response returned in 202 error code
> ----------------------------------------
>                 Key: AXIS-1845
>                 URL:
>             Project: Axis
>          Issue Type: Bug
>         Environment: Axis 1.2RC3
>            Reporter: Amanda Hopgood
>            Priority: Minor
> I have a system using Axis 1.2 RC3 which is communicating with a remote application.
The remote application sends back 202 for success with a SOAPResponse in. Our application
is expected to be able to decode the soapresponse returned.
> However we are using the standard HTTPSender, and this has code that means that the SOAPResponse
is not decoded by Axis if its in a 202.
> This appears to be controlled by the readFromSocket method in the HTTPSender where it
>  	if ((returnCode > 199) && (returnCode < 300)) {
>         	if (returnCode == 202)
>             	return inp;
>             // SOAP return is OK - so fall through
> However the equivalent code doesn't appear to be in the CommonsHTTPSender (but we have
other problems using Commons).
> Is it possible to update the current HTTPSender to remove the special case of 202, or
make it configurable as to whether it treats 202 as a special case, or provide an extra sender
that is same as HTTPSender but doesn't treat 202 differently to 200.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message