Groups: Administration
Joined: 11/3/2005(UTC)
Posts: 2,253
Thanks: 28 times
Was thanked: 60 time(s) in 59 post(s)
|
Hi, Orcus.
Yes, Cassini 1.1 fully supports WSE 2.0. There might be a couple of reasons why you get null while trying to access SoapContext from your web service method - though both would lead to null SoapContext under IIS as well as Cassini:
1) You use WS client that doesn't send WS-* headers. For example, if you use web browser to point to your http://localhost:port/WebService1.asmx - you will get null under IIS and Cassini. Your client needs to talk WS-* for your service to get SoapContext. Make sure when you build your client, you add WSE 2.0 support first, then add Web Reference pointing to your web service, and third, out of two versions of the client proxy classes, instantiate one that ends with "Wse", like "new localhost.Service1Wse()".
2) This may sound silly, but make sure you access WSE.RequestSoapContext.Current, not WSE.SoapContext.Current in your web service.
Again, both scenarios will return null SoapContext under IIS as well as Cassini if not implemented correclty.
Best regards,
UltiDev Team.Please donate at http://www.ultidev.com/products/Donate.aspx to help us improve our products.
|
