Further to my earlier email....
The response (results()) is null when the method call returns from the
webservice as per the following code in the proxy class:
Dim results() As Object = Me.Invoke("process3ParmRequest", New
Object() {inputHeader, messageControlPayload, inputMessage})
The results of the immediate window are:
?results(0)
Nothing
...Jit.
Try refreshing the proxy. When you see a null response coming back, it
often means that the serializer did not see the right content that it
expected on the wire.
Regards
Dan Rogers
Microsoft Corporation
--------------------
Thread-Topic: Soap Response
thread-index: AcTHdLDViDg9mhfyRkuSypob6ADBaA==
X-WBNR-Posting-Host: 210.55.201.197
From: "=?Utf-8?B?Sml0IFByYXNhZA==?=" <JitPrasad@discussions.microsoft.com>
References: <596D72F5-4148-4DFD-83E6-B308F433F7EA@microsoft.com>
Subject: RE: Soap Response
Date: Wed, 10 Nov 2004 14:29:07 -0800
Lines: 170
Message-ID: <F733DE2F-B20E-4D85-A99A-3723EA4DC09A@microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: cpmsftngxa10.phx.gbl
microsoft.public.dotnet.framework.webservices:7359
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices
Further to my earlier email....
The response (results()) is null when the method call returns from the
webservice as per the following code in the proxy class:
Dim results() As Object = Me.Invoke("process3ParmRequest", New
Object() {inputHeader, messageControlPayload, inputMessage})
The results of the immediate window are:
?results(0)
Nothing
..Jit.
> I have been consuming a IBM Websphere (Java) web service using .Net 1.0 front
> end writen in VB.NET. The proxy class submits a soap request and gets a soap
[quoted text clipped - 34 lines]
> <s:sequence>
> <s:element minOccurs="0" maxOccurs="1"
name="process3ParmRequestResult"
> type="s:string"/>
> </s:sequence>
[quoted text clipped - 39 lines]
>
> Proxy Class...
'---------------------------------------------------------------------------
---
> ' <autogenerated>
> ' This code was generated by a tool.
[quoted text clipped - 3 lines]
> ' the code is regenerated.
> ' </autogenerated>
'---------------------------------------------------------------------------
---
> Option Strict Off
> Option Explicit On
[quoted text clipped - 14 lines]
> System.ComponentModel.DesignerCategoryAttribute("code"), _
>
System.Web.Services.WebServiceBindingAttribute(Name:="GTPSRouterServiceSoap"
,
> [Namespace]:="urn:ServiceRequest")> _
> Public Class GTPSRouterService
[quoted text clipped - 8 lines]
> '<remarks/>
>
<System.Web.Services.Protocols.SoapDocumentMethodAttribute("urn:ServiceReque
st/process3ParmRequest", _
>
> RequestNamespace:="urn:ServiceRequest", _
[quoted text clipped - 3 lines]
> Use:=System.Web.Services.Description.SoapBindingUse.Encoded, _
>
ParameterStyle:=System.Web.Services.Protocols.SoapParameterStyle.Wrapped)> _
> Public Function process3ParmRequest(ByVal inputHeader As String, ByVal
> messageControlPayload As String, ByVal inputMessage As String) As String
[quoted text clipped - 19 lines]
> End Function
> End Class
MSDN Andi - 22 Mar 2005 13:02 GMT
Hi,
I pretty much have the same problem like Jit.
It worked under 1.0 it does not work under 1.1
In my case I have also "encoded" SoapBinding-use and SoapParameterStyle
"wrapped".
I recompiled the whole project using .NET 1.1
I even intercepted the dynamically generated code and even disassambled it.
No actual difference in program flow and program logic.
However, the .NET 1.1 Framework returns nothing instead of the XML-string.
I had the SOAP-sniffer of the Soap Toolkit 3.0 running - and the return
string ist just fine... just under .NET 1.1 I get a "nothing" response.
I have no way of further debugging what happens after the ".invoke" call,
since the framework hides the rest of the processing.
I tried to tackle this quite a while now and I find traces here and there
online that several people have the same problem.
All of them communicating with non-.net-based systems of some sort.
Regards,
Andi
> Try refreshing the proxy. When you see a null response coming back, it
> often means that the serializer did not see the right content that it
[quoted text clipped - 216 lines]
> > End Function
> > End Class