[AXISCPP-914] fault/exception/error handling flawed

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.6 Alpha
• Fix Version/s: current (nightly)
• Component/s: Client - Stub
• Environment: WIN2KSP4 JDK1.5.0_06 MSVC6SP6
• Assignee: Unassigned
• Reporter: Franz Fehringer
• Created: 21/Jan/06 03:15
• Updated: 18/Jan/07 05:24
• Resolved: 18/Jan/07 05:24

Description

fault/exception/error handling seems to be flawed in several respects (in what follows i refer to my attached example).
First the intention of the WSDL/XSD writers clearly was to expect an ErrorResponse element inside the soap:faultdetail for the error scenario of all three requests (and i think they are right so).
The Axis generated code instead looks for LoginFault, LogoutFault and SearchRoomsFault.
Second there seem to be problems with memory management.
I get user defined breakpoints and/or access violations at (all in PegsPortType.cpp)
throw fault; // line 588
delete [] const_cast<char*>(detail); // lines 615,720,879
The const_cast as well as the interplay between assignment and delete operations generally look fishy too me.
In my investigations i stumbled over the generated t_ErrorResponse (derived from SoapFaultException) copy constructor.
The base class is not copied over there.
More to follow.