NonStop SOAP User's Manual
Customizing the SOAP Server
NonStop SOAP User’s Manual—520501-012
8-46
Files Released and Generated
To log a message only to the trace file, call this function:
gSoapTrace.log(
message
);
where 
message
 is a message of your choice, enclosed in quotation marks or a 
character buffer (char *). 
For general information about error reporting in NonStop SOAP, see Error Log File on 
page 4-69.
Files Released and Generated
The files released as part of the NonStop SOAP 3.0 product include:
•
SoapUEHandler.h, ServiceEnv.h, ServiceReqResponse.h, Attachment.h, 
AttachmentManager.h, UESoapHeader.h, UESoapHeaderManager.h, SoapFault.h, 
and SoapUEClassFactory.h.
•
You cannot modify header files in this category. SoapUEHandler_impl.cpp is 
released as an empty file where you need to add #include statements to include all 
*.cpp files implementing user-exits. 
Files generated by the SOAP Admin tool:
•
SoapUEClassFactory.cpp, SoapUEHandler_impl.h, SoapUEHandler_impl.cpp, and 
Makefile
You can customize the generated files as needed. You can provide implementations 
for classes declared in SoapUEHandler_impl.h. 
SoapUEClassFactory.cpp is used to instantiate a user-exit object. The SOAP 
server takes the responsibility to release the object when it is appropriate. 
SoapUEHandler_impl.h consists of class declarations of all user-exits. For example, 
suppose user-exits need to be generated for this Pathway service:
•
PATHWAY service EmpInfo
Then SoapUEHandler_impl.h consists of these class declarations:
•
SoapPW_UEHandler_EmpInfo
•
SoapUEHandler_Generic
Each class is derived from SoapUEHandler. The class factory instantiates a 
SoapUEHandler_Generic object which contains an internal SoapUEHandler 
corresponding to a Pathway service.










