""Peter Huang" [MSFT]" wrote:

> Hi
>
> I think you may try to follow the link below to access a Web Service from
> C++.
> Walkthrough: Accessing an XML Web Service Using C++
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsent7/html
> /vbwlkwalkthroughusingwebservicewithunmanagedcode.asp
>
> The code above will use ATL class CSoapSocketClientT to access the Web
> Service.
> CSoapSocketClientT Class
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/
> vclrfCSoapSocketClientT.asp
> ============================================================================
> ================================
> This class conforms to ATL Server's SOAP client archetype.
>
> Typically this class is used with SPROXY-generated classes which build up
> the SOAP messages for you, but it is possible to use this class
> independently in the following way:
>
> Create an instance and pass the location of the XML Web service to the
> constructor.
>
> Call SetProxy or SetTimeout if necessary.
>
> Call GetWriteStream and write the SOAP message to that stream.
>
> Call SendRequest to send the SOAP message to the server.
>
> If SendRequest succeeded, call GetReadStream to read the SOAP response.
>
> If SendRequest failed, call GetClientError and GetStatusCode, or look at
> m_fault for error information.
>
> Call CleanupClient before returning to Step 3 to send further messages.
> ============================================================================
> ================================
> Here is C++ code snippet to access webservice.
> void AccessService(){
>     using namespace std;
>     Service::CService ws;
>     CComBSTR bstr;
>     HRESULT hr = ws.HelloWorld(&bstr);
>     if (SUCCEEDED(hr))
>     {
>         CW2A printstr(bstr);
>         cout<<"C++"<<endl;
>         cout<<printstr<<endl;
>     }
>     else
>     {
>         cout<<ws.GetStatusCode()<<endl;
>         cout<< "An error occurred: "<<hex<<hr<< endl;
>     }
> }
>
> int _tmain(int argc, _TCHAR* argv[])
> {
>     if (SUCCEEDED(CoInitialize(NULL))){
>         AccessService();
>         CoUninitialize();
>     }
>     return 0;
> }
>
> NOTE: we can try to use the ws.GetStatusCode() to get the StatusCode e.g.
> 401.
>
> If I have any misunderstanding, please feel free to post here.
>
>
>
> Best regards,
>
> Peter Huang
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>

""Peter Huang" [MSFT]" wrote:

> Hi
>
> I am sorry. It seems that I did not understanding your scenario very clear.
> From your description, you have two test solutions.
> 1. pure .NET
> .NET client --->proxy---->Web Service
> You will get 407, which means the proxy need authentication. You did not
> have concern with the scenario or you want to know how to make the .NET
> client call Web Service successfully without the 407 error.
>
> 2. Com Interop
> Refer to my last post about how to call Web Service from C++.
> If you mean the scenario as below.
> C++ client ----> .NET class libray----->proxy----->Web Service
>
> The C++ client called .NET class library via Com Interop.
> You want to know why the C++ client did not get the 407 error. If this is
> not the case please let me know.
> This involved the fact that .NET and COM have their own error handling
> mechanism.
> Error Handling
> http://msdn.microsoft.com/msdnmag/issues/01/08/Interop/
>
> Handling COM Interop Exceptions
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/htm
> l/cpconhandlingcominteropexceptions.asp
>
> HRESULTs and Exceptions
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/htm
> l/cpconHRESULTsExceptions.asp
>
>
> Best regards,
>
> Peter Huang
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>

""Peter Huang" [MSFT]" wrote:

> Hi
>
> So far I understand your scenario you are going the second test solution in
> my last post.
> C++ client ----> .NET class library----->proxy----->Web Service
>
> In the .NET class library, you are using the same code with the .NET test
> client.
> But in the  .NET class library you will not get 407 response. You will just
> get a underlying connection is closed¡§error or just hang in .NET 2.0.
> If I misunderstood, please feel free to post here.
>
> For this scenario, I think you may try to use netmon tool to see what will
> return from the proxy or if it has returned from the proxy.
> Microsoft have netmon tool shipped with SMS server.
> You may try the netmon tool in the link below.
> http://www.netmon.org/tools.htm#Sniffers
>
> Best regards,
>
> Peter Huang
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>

""Peter Huang" [MSFT]" wrote:

> Hi
>
> First I think we need to confirm what is your scenario with Com Interop
> solution.
> C++ client ----> .NET class library----->proxy----->Web Service
>
> If it is the problem at the above one, then the problem occurred in .NET
> class library----->proxy----->Web Service should did not be related with
> Com interop.
> Becaused the problem is all occurred in the .NET library called web service.
>
> If I misunderstand, please correct me.
> If you want to handle exception across Com interop layer.
>
> I htink you may try to have a look at the information below about how to
> handle exception between .NET and COM via Com inerop wrap.
> This involved the fact that .NET and COM have their own error handling
> mechanism.
> Error Handling
> http://msdn.microsoft.com/msdnmag/issues/01/08/Interop/
>
> Handling COM Interop Exceptions
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/htm
> l/cpconhandlingcominteropexceptions.asp
>
> HRESULTs and Exceptions
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/htm
> l/cpconHRESULTsExceptions.asp
>
>
>
>
> Best regards,
>
> Peter Huang
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>