Re: SOAP Toolkit client problems with DotNet Service
- From: "Shailen Sukul" <shane@xxxxxxxxxxxxx>
- Date: Mon, 15 Jan 2007 13:54:07 +1100
Sounds like the fully qualified name of your object has changed when you
repointed it.
try changing your proxy's business objects to the new namespace.
HTH.
--
With Regards
Shailen Sukul
..Net Architect
(MCPD: Ent Apps, MCSD.Net MCSD MCAD)
Ashlen Consulting Services
http://www.ashlen.net.au
"Michael Russell" <mr_b15h0p@xxxxxxxxxxx> wrote in message
news:eVWMEZnNHHA.5016@xxxxxxxxxxxxxxxxxxxxxxx
Hi all,
I'm trying to get a client working with my ASP.NET web service. The
client's been working great up to this point with a SOAP Toolkit-generated
service based on a VB COM library.
On the client side, I'm calling the web service here:
--
Dim soapClient As SoapClient30
Dim xmlList As IXMLDOMNodeList
Set soapClient = GetSoapConnection
Set xmlList = soapClient.GetGroups(SYSTEM_NAME)
--
and at that last line, I get a "424 - Object required" error.
I haven't modified the code at all except to point to the new WSDL.
In the debugger I can see that "soapClient.GetGroups(SYSTEM_NAME)"
contains a list of Nodes, so it's calling the service and successfully
retrieving the message, but it refuses to process it.
Any guidance on this would be GREATLY appreciated.
.
- Follow-Ups:
- Re: SOAP Toolkit client problems with DotNet Service
- From: Michael Russell
- Re: SOAP Toolkit client problems with DotNet Service
- References:
- SOAP Toolkit client problems with DotNet Service
- From: Michael Russell
- SOAP Toolkit client problems with DotNet Service
- Prev by Date: Re: Deploying ASP.NET 2.0 Applications in IIS 6.0
- Next by Date: web service overwriting web app folder
- Previous by thread: SOAP Toolkit client problems with DotNet Service
- Next by thread: Re: SOAP Toolkit client problems with DotNet Service
- Index(es):
Relevant Pages
|
Loading