|
|
|
|
|
Total Hits: 207 | Today: 0 |
|
Rating:
|
|
|
When you use the low-level Application Programming Interface (API)
SoapSerializer component from a process other than the ASP listener on the server, you encounter unexpected behavior.The SoapSerializer object provides a mechanism to manually build a Simple Object Access Protocol (SOAP) message. You can use SoapSerializer in a low-level API scenario on the server to build up the SOAP Response message. In this case, SoapSerializer is initialized with the Active Server Pages (ASP) Response object. If the SoapSerializer calls are made from a process other than the ASP Listener, as in the following scenarios, you receive unexpected results:
- The SoapSerializer calls are made from a Component Object Model (COM) component that is placed in a COM+ server application.
- The SoapSerializer calls are made from a COM component that is placed in a Microsoft Transaction Server (MTS) server package.
- The SoapSerializer calls are made from a COM component that is being debugged from the Microsoft Visual Basic Integrated Development Environment (IDE).
In all three scenarios, SoapSerializer calls are made from a process other than the ASP Listener. This problem does not affect any high-level API scenarios (such as the SoapClient or the SoapServer object).
|
|
|
|
Latest Posts at Dev Forums
|
|
|
|
|
|
|
|
|
|
|
