.NET client cannot talk to Axis web service

[Jarmo]

I have a Java-based (Axis) Web Service and am trying to write a .NET client
in C#. I run into two different problems.

1. if the WSDL was generated using the Axis defaults then .NET cannot update
its web reference. It complains that datatype 'String' is undefined.
Strangely, the WSDL returned by the WS to a browser is quite different to
that which Visual Studio appears to import and write locally. The latter,
for example, indicates different definitions for every single string e.g.
q1:string, q2:string through q55:string.

2. if the WSDL is generated using java2wsdl and wrapped/literal is requested
then Visual Studio *can* update it web reference and I can build my project
but when it runs I get "root element is missing" XML exceptions.

Given that the WSDL was auto-generated in both cases and my project is quite
simple, I'd expect both styles to just work out of the box. I'm blocked on
both fronts. Any help would be greatly appreciated.

[FWiegand]

i had the same issue within dotnet itself. i called a dotnet webservice
from a dotnet.client.
i dont know what it is exactly but it seems to me that attribute or
element values contain unquoted or 'bad' characters.
have a look on your example content.

falk
Jarmo wrote:

*I have a Java-based (Axis) Web Service and am trying to write a .NET
client
in C#. I run into two different problems.

1. if the WSDL was generated using the Axis defaults then .NET cannot
update
its web reference. It complains that datatype 'String' is
undefined.
Strangely, the WSDL returned by the WS to a browser is quite
different to
that which Visual Studio appears to import and write locally. The
latter,
for example, indicates different definitions for every single string
e.g.
q1:string, q2:string through q55:string.

2. if the WSDL is generated using java2wsdl and wrapped/literal is
requested
then Visual Studio *can* update it web reference and I can build my
project
but when it runs I get "root element is missing" XML exceptions.

Given that the WSDL was auto-generated in both cases and my project
is quite
simple, I'd expect both styles to just work out of the box. I'm
blocked on
both fronts. Any help would be greatly appreciated. *

--
FWiegand
------------------------------------------------------------------------
Posted via http://www.mcse.ms
------------------------------------------------------------------------
View this thread: http://www.mcse.ms/message1806717.html

[Marvin Smit]

Hi,

I think two different issues are mentioned here.

The FWiegand issue sounds like "unescaped XML" being send. The issue
from the original post is more (de-)serialization based.

When building WebServices, once should realize, its just a set of
standards defined for communication across boundaries. Axis & WSE are
toolkit that implement these specifications for you and allow you to
approach them programatically.

About the undefined String type; Not having the WSDL to look at makes
this hard.

A few things to take care of in your WSDL;
- Use Document / Literal
- Use Wrapped parameter style
- Design from XSD perspective (no platform specific types like .Net's
'DataSet' or Java's 'String', but XSD sequences & xsd:string)

Hope this helps,

Marvin Smit.

On Mon, 5 Sep 2005 15:20:00 -0500, FWiegand
<FW*************@mail.mcse.ms> wrote:

i had the same issue within dotnet itself. i called a dotnet webservice
from a dotnet.client.
i dont know what it is exactly but it seems to me that attribute or
element values contain unquoted or 'bad' characters.
have a look on your example content.

falk
Jarmo wrote:

*I have a Java-based (Axis) Web Service and am trying to write a .NET
client
in C#. I run into two different problems.

1. if the WSDL was generated using the Axis defaults then .NET cannot
update
its web reference. It complains that datatype 'String' is
undefined.
Strangely, the WSDL returned by the WS to a browser is quite
different to
that which Visual Studio appears to import and write locally. The
latter,
for example, indicates different definitions for every single string
e.g.
q1:string, q2:string through q55:string.

2. if the WSDL is generated using java2wsdl and wrapped/literal is
requested
then Visual Studio *can* update it web reference and I can build my
project
but when it runs I get "root element is missing" XML exceptions.

Given that the WSDL was auto-generated in both cases and my project
is quite
simple, I'd expect both styles to just work out of the box. I'm
blocked on
both fronts. Any help would be greatly appreciated. *