Re: .NET does not take WSDL generated by Axis

[butek]

Well, there are two issues here. One, as Steve pointed out, is an interoperability issue. No spec exists which defines how to send a hashtable, map, etc. across the wire in an interoperable manner such that the other side knows it can fluff it back up into something its language knows about. But even if a side doesn't know how to fluff it into something it knows about (ie., a Java HashMap or Hashtable), it should create SOMETHING (ie., a Java bean).

Second, it sounds to me like .NET's wsdl.exe cannot handle AXIS's generated WSDL. The WSDL looks perfectly legal to me, so unless someone can point out that AXIS's WSDL is illegal, then this is a .NET problem.

Russell Butek
[EMAIL PROTECTED]

Please respond to [EMAIL PROTECTED]

To: <[EMAIL PROTECTED]>
cc:
Subject: Re: .NET does not take WSDL generated by Axis




----- Original Message -----
From: "Steve Loughran" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 15, 2002 3:23 PM
Subject: Re: .NET does not take WSDL generated by Axis

>
> ----- Original Message -----
> From: "Naresh Bhatia" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, July 14, 2002 19:58
> Subject: RE: .NET does not take WSDL generated by Axis
>
>
> > After a bit of experimentation with the WSDL generated by Java2WSDL, I
> found
> > that .NET does not like the declaration of a camplexType Map:
>
> um, you cant send maps, hashtables and the like from Axis to .NET, not yet,
> the 'hashtable' problem as we call it. An ongoing soapbuilder task.

Because I'm not too sure what soapbuilder is, could you tell me is it�a problem�with axis, .NET, or the soap spec?

�
> A todo item is for someone (me if nobody else) to add a lot more to the axis
> docs on interop and good and bad stuff to send over the wire.