DO NOT REPLY [Bug 15933] New: - HTTP response status codes arent being set as per the SOAP spec

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15933>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15933

HTTP response status codes arent being set as per the SOAP spec

           Summary: HTTP response status codes arent being set as per the
                    SOAP spec
           Product: Axis
           Version: current (nightly)
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Basic Architecture
        AssignedTo: axis-dev@xml.apache.org
        ReportedBy: stevel@apache.org


SOAP 1.2 says what error codes we should send back
(http://www.w3.org/TR/2002/CR-soap12-part2-20021219/#http-respbindprocess) , but
we always send back a 500, except for unauth, which generates a 401. 

We need to fix this. Here are some options
(a) extend the string matching in AxisServlet to check for other errors and set
the status appropriately

(b) pull the fault-to-status-code mapping out into a mapper class for easier
switching between versions.

(c) Have subclasses of AxisFault and have the appropriate subclasses used where
appropriate.

(d) add a statusCode property to AxisFault, to let people override the default
value(500) when desired.

Thoughts? (a) is the simplest and could be done for 1.1. easily, but the others
may be better long term. (b) and (c) hide the fault options from the handlers,
so give Axis control of the values, which may be better longer term, esp if
successors to SOAP1.2 want to change any of the rules.