Mauro, Of course I understand your practical point exactly and I would very much appreciate easier DOTNET-compatibility too- however:
interoperability can realistically only be achieved in areas where standards have been established already (in our real world) For better or worse, there are no official WS-standards for expressing Null-Values of programming languages, DB-Nulls, and much more. (Nor will the two of us be able to establish it now, let alone enforce it - so again: outside of standards its up to the programmer methinks) The central piece of a Web Service is, conceptually, a WSDL-definition (description of interface/contract) I am sure a Web Service based on a WS-I conforming WSDL-definition can be called by DOTNET-Clients with no problem, same as by all other WS-I-conforming Clients. (Otherwise twould be a Microsoft-bug) Ask Microsoft about it. WS-I was after all co-founded by Microsoft. So pls demonstrate where exactly an AXIS-generated WSDL is not conforming to these standards. This really would be an AXIS-bug to attend to then. Some new pseudostandard JAVA2DOTNET (which versions of each anyway, what about future developments?) is looking like a dead horse to me. Many of the webservices out there, and in fact, all public ones, have to be reachable by non DOTNET-clients. Maybe even yours - someday! Cheers Wolfgang --- On Thu, 1/7/10, Mauro Molinari <mauro.molin...@cardinis.com> wrote: > From: Mauro Molinari <mauro.molin...@cardinis.com> > Subject: Re: [jira] Commented: (AXIS2-3300) minOccurs="0" always generated by > Java2WSDL - problems with .NET client generation > To: axis-dev@ws.apache.org > Date: Thursday, January 7, 2010, 12:16 PM > WJ Krpelan ha scritto: > > Dear ppl, I think this leads us nowhere. Webservices > is neither JAVA > > nor DOTNET nor PHP nor PERL-specific nor should > it be. Webservices > > is expected to interoperate with all of them. How is > this to be > > accomplished? By adhering to the standards laid down > for WSDL. So > > PLEASE restrain yourself to using language constructs > which can be > > clearly defined within the reach of WSDL/XML-Schema, > and keep it > > simple on top of that. It is the JAVA-Programmers or > > DOTNET-Programmers duty to guarantee that unproper > values are not put > > into WS-clients or WS-Server-stubs!! Cheers, Wolfgang > > In an ideal world, I would perfectly agree with you. > > In a real world, given the importance and market share of > .NET, if tools provided by Axis2 don't let me write web > services that are correctly callable by .NET clients, I > would consider them to be completely useless. > > Moreover, please notice that the discussion is all about > adhering to the standards, but in the way that grants > interoperation the most in real-world common scenarios. > > -- Mauro Molinari > Software Designer & Developer > E-mail: mauro.molin...@cardinis.com >
