Re: [SOAP] Help with .NET client
| From: | Ron Pedde | Date: | Wed, 16 Jul 2003 22:01:17 +0000 |
| Subject: | Re: [SOAP] Help with .NET client | ||
| References: | 1 2 | Groups: | php.soap |
| Request: | Send a blank email to php-soap+get-832@lists.php.net to get a copy of this message | ||
On Wed, Jul 16, 2003 at 05:15:41PM -0400, Alok K. Dhir wrote:
> My typedef is defined as follows:
>
> $this->__typedef['StudentObject'] = array(
> 'student_id' => 'string',
> 'lastlogin' => 'string'
<snip>
> );
>
I was having trouble returning a complex type to a vs.net consumer.
When I took a close look at the wsdl, I noticed that the return type
of the function that returned the struct (of type ConfigEntry) looked
like this:
<message name="getConfigResponse">
<part name="outputStruct" type="xsd:ConfigEntry" />
</message>
I changed the 'type="xsd:ConfigEntry"' to
'type="tns:ConfigEntry"' and
suddenly everything worked great -- c#.net generated the right proxy
code and everything was wonderful.
My questions, then, are:
1. Is this the same problem you are having?
2. Is this a problem with the wsdl generator?
3. Or is this a problem with my __typedefs?
I can provide my typedefs and the full wsdl to anyone that has some
insight on this. Additionally, if someone can help me get this
working right, I'd be more than happy to put together a nice
"Pear::SOAP - VS.net HOWTO"... that way maybe we can get some good
examples to help get rid of these list messages... I can't seem to
find any non-trivial examples of vs.net consuming *any* web services
besides asp.net ones.
Thanks.
--
Ron Pedde
ron@corbey.com