Problem with complex types when consuming Axis 1.4 web service with C# client -- dotnet web services

dotnet web services : Problem with complex types when consuming Axis 1.4 web service with C# client

John Saunders
3/6/2007 1:31:09 PM

[quoted text, click to view]

This often happens when there is a confusion of namespaces between the
client and the server. Make sure that your .NET code is expecting the exact
same namespaces as the Axis code is sending.

When I say "exact", I mean byte-for-byte exact. A recent poster had a
problem because there was a trailing space in the namespace declaration he
was using.

John

Philip Reimer
3/6/2007 2:39:45 PM

Hello.

We have here a Java web service that has been created using Apache Axis
1.4, using the document/literal wrapped style, and returns complex types
in its methods.

When consuming the web service with a C# client, all the fields in the
returned objects are null. The SOAP message, however, contains all the
expected data.

I've already searched on the net but only found people describing the
same problem but no solutions for this.

So, if anyone could point me to some documentation about that or have
some solution, I'd appreciate if he'd let me know.

Regards,

Philip Reimer
3/7/2007 1:00:55 PM

John Saunders schrieb:
[quoted text, click to view]

Hi John.

Thanks a lot. That seems to have been the problem here.

Greetings,

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about dotnet web services

home · blog · groups

Questions? Comments? Contact the dn