Hi Danny,
I looked at this WSDL, and then tried it out. From what I can see, there
is no web service at the specified URL. Since the WSDL specifices a URL,
this is the one I tried. The URL cannot be resolved (e.g. the SOAP request
is rejected by the server).
I notice that there is no SOAP Action specified... is it possible that your
web service requires a specific SOAP action? I also noted that unqualified
elements are called for... I really need to see the XML that you think is
being returned. If you took the proxy code you have on this site and used
it, I suspect that you are also getting a rejected request - which will
make your ASP.net test script expose a null (I'm assuming you have ignore
all errors enabled in your test environment).
The WSDL itself has some oddities. The schema target namespace and the
WSDL target namespace are identical - and this is also the URL for the
service endpoint. Since each represents a version reference (in the first
two cases) and a service callable end point (the latter case) this is
unusual Regardless, it looks like add-web-reference is doing what you
asked.
Where did this WSDL come from? Did you hand code it? I am not familiar
with how Axis plays with the XML or the SOAP packet on the wire... or did
Axis create this WSDL file for you?
I hope this helps
Dan
--------------------
Date: Tue, 07 Dec 2004 07:48:18 +0000
From: Danny Tuppeny <da***@nospam.o ops>
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: microsoft.publi c.dotnet.framew ork.webservices
Subject: Re: Axis. Object properties are null (serialisation problem?)
References: <41************ ***********@ptn-nntp-reader03.plus.n et>
<S5************ **@cpmsftngxa10 .phx.gbl>
<41************ ***********@ptn-nntp-reader01.plus.n et>
<0D************ *@cpmsftngxa10. phx.gbl>
In-Reply-To: <0D************ *@cpmsftngxa10. phx.gbl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Lines: 14
Message-ID: <41************ ***********@ptn-nntp-reader04.plus.n et>
Organization: Customer of PlusNet plc (
http://www.plus.net)
NNTP-Posting-Host: f7f7a0fe.ptn-nntp-reader04.plus.n et
X-Trace:
DXC=H>5SoDSQleZ BX8>[M_9^HWigd3Y`7Rb ;^3_LeXC3B]SY4j?]]JUIF5P9CE@6OHlA 3PGa_01j
mm<WQ@25M[oR06Q[
X-Complaints-To:
ab***@plus.net
Path:
cpmsftngxa10.ph x.gbl!TK2MSFTNG XA03.phx.gbl!TK 2MSFTNGP08.phx. gbl!newsfeed00. s
ul.t-online.de!t-online.de!news. zanker.org!nntp-peering.plus.ne t!ptn-nntp-fe
eder01.plus.net !ptn-nntp-spool01.plus.ne t!ptn-nntp-reader04.plus.n et!not-for
-mail
Xref: cpmsftngxa10.ph x.gbl
microsoft.publi c.dotnet.framew ork.webservices :7934
X-Tomcat-NG: microsoft.publi c.dotnet.framew ork.webservices
Dan Rogers wrote:
If everything is coming up null, it's almost certain that you are seeing
namespace mismatch.
I've updated all the files here:
http://dantup.me.uk/SoapProb/
Afraid I can't get a copy of the soap envelopes from here, but if you
can see anything with the WSDL, any suggestions would be much appreciated.
Thanks,
Danny