[ http://issues.apache.org/jira/browse/AXISCPP-705?page=all ]
Samisa Abeysinghe closed AXISCPP-705:
-------------------------------------
Resolution: Fixed
Fix to the issue AXISCPP-322 resolves this issue too.
Care must be taken in adding new values to AXISC_EXCEPTIONS in the future. The
additions must have a matching entry in s_arrLocalFaultStruct of
src/soap/SoapFault.cpp
> enum AXISC_EXCEPTIONS used as index for SoapFaultStruct -- but they don't
> match
> -------------------------------------------------------------------------------
>
> Key: AXISCPP-705
> URL: http://issues.apache.org/jira/browse/AXISCPP-705
> Project: Axis-C++
> Type: Bug
> Components: Server - Engine
> Versions: current (nightly)
> Environment: Windows XP Pro, VS2003
> Reporter: Henrik Nordberg
> Assignee: Samisa Abeysinghe
>
> SoapFault* SoapFault::getSoapFault(int iFaultCode) has the following line:
> string strFaultcode = s_parrSoapFaultStruct[iFaultCode].pcFaultcode;
> where iFaultCode is passed in as the result of this call:
> Status = engine->process(pStream);
> Satus becomes 69 in the situation I am debugging. This value is defined as
> SERVER_CLIENT_ENGINE_MISMATCH in AXISC_EXCEPTIONS but SoapFaultStruct only
> has values up to 52 and the descriptions don't seem to match the
> corresponding values in AXISC_EXCEPTIONS. Something is seriously wrong
> here....
> string strFaultcode = s_parrSoapFaultStruct[iFaultCode].pcFaultcode; crashes
> since s_parrSoapFaultStruct has no entry for iFaultCode == 69.
--
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
