[ http://issues.apache.org/jira/browse/AXISCPP-866?page=comments#action_12357863 ]
James Jose commented on AXISCPP-866: ------------------------------------ Even if the server send a fault message which is defined in the WSDL file, the client engine only generates AxisException. Because of this issue several tests like FaultMappingDoc, FaultMappingRepeatedDoc.. failing. e.what() method of AxesException giving the following error message for all Exception Exception : HTTPTransportException:HTTP transport error Server sent HTTP error: 'Internal Server Error' In the DynamicCheckFault Test when checkFault() method of Call class is invoked , an exception is generated.. > Client fails to handle fault messages from the server > ----------------------------------------------------- > > Key: AXISCPP-866 > URL: http://issues.apache.org/jira/browse/AXISCPP-866 > Project: Axis-C++ > Type: Bug > Components: Client - Deserialization > Reporter: James Jose > > Server sends the following fault message. But client fails to handle the > fault message and results in Exception > <?xml version="1.0" encoding="utf-8"?> > <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";><soapenv:Header/><soapenv:Body><soapenv:Fault><faultcode > xmlns="">Server.generalException</faultcode><faultstring > xmlns="">org.xml.sax.SAXException: WSWS3052E: Error: Bad envelope namespace: > http://www.w3.org/2003/05/soap-envelope To see the message containing the > parsing error in the log, either enable web service engine tracing or set > MessageContext.setHighFidelity(true).</faultstring><detail > xmlns=""/></soapenv:Fault></soapenv:Body></soapenv:Envelope> > Exception generated by the client: > Exception : HTTPTransportException:HTTP transport error > Server sent HTTP error: 'Internal Server Error' > DynamicCheckFaultTest fails because of this issue... -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira
