Wednesday, May 07, 2003 6:52 PM
Jan Tielens
Eureka! SoapExtension problems solved!
Maybe you've read my post about the problems I had while using a custom SoapExtension class. Thanks to an anonymous reaction, I found the sollution!! I was testing the webservice by using the default test page from Internet Explorer, but the testpage in IE uses the GET protocol, not the SOAP protocol. So there was nothing wrong with my code (I started believing I really sucked ;-), I only had to make a very simple test application. Thanks again to the person who submitted this tip!
So the result was that I had an application that showed the encrypted data... After some searching I discovered that I needed to alter the Reference.vb file manually and add an extra attribute on the Webservice proxy method:
<System.Web.Services.Protocols.SoapDocumentMethodAttribute("http://tempuri.org/TestEncr/Service1/TestMe", RequestNamespace:="http://tempuri.org/TestEncr/Service1", ResponseNamespace:="http://tempuri.org/TestEncr/Service1", Use:=System.Web.Services.Description.SoapBindingUse.Literal, ParameterStyle:=System.Web.Services.Protocols.SoapParameterStyle.Wrapped) _
, EncryptionExtension(decrypt:=DecryptMode.Response)> _
Public Function TestMe() As String
Dim results() As Object = Me.Invoke("TestMe", New Object(-1) {})
Return CType(results(0), String)
End Function
It's great to have such a nice community of people to help you out!