There are ways around it. Just of the top of my head I can think of 2. 1. reverse-engineer the dataset schema, build a WSDL that specifies the stuff you want, then build your java client from that.
2. build a .NET bridge app - that consumes the webservice, and exposes a different interface. The .NET app should get the DataSet, then transform that into an array of typed objects. Your Java client should then call the bridge app. -----Original Message----- From: Ralf Bust [mailto:[EMAIL PROTECTED] Sent: Friday, April 01, 2005 5:14 AM To: axis-user@ws.apache.org Subject: Re: Newbie Question / .NET SOAP Service / Dataset / any / WSDL2Ja va Yes, you are right. I totally agree. But usually for me as a client developer it is impossible to change anything on the server side :( I totally agree that programming first and generate the WSDL is totaly wrong. But is the only answer to my problem that AXIS is unusable for a service that uses MS Datasets? I am not going to imagine the amount of time implementing this client by hand :( rb Ruiz González, Jose de Jesus schrieb: > Sorry, I posted my answer to another thread. > > As a Java Client, you never mind wich Database access technology a Web > Service uses. > That is the functionality of a Web Service, it´s an interface between > your java Client And some (unknown) database. > > > José de Jesús Ruiz Gonzalez > Departamento de Sistemas > México Asistencia S.A. de C.V. > Sistema Internacional de Asistencia Mapfre > > * mailto:[EMAIL PROTECTED] > *(52) 55 + 54801298 > > *Fax(52) 55 + 56112011 > > <http://www.mexicoasistencia.com/> > > > -----Mensaje original----- > De: Dino Chiesa [mailto:[EMAIL PROTECTED] Enviado el: Miércoles, > 30 de Marzo de 2005 03:36 a.m. > Para: axis-user@ws.apache.org > Asunto: RE: Newbie Question / .NET SOAP Service / Dataset / any / > WSDL2Java > > > Is Axis capable of using Datasets? > > No. > > You could do it, but it would be painful and expensive. > > Your service ought not to use Datasets, if it is intended to be > interoperable with Java/AXIS, or any other non-.NET webservices stack. > > This is a classic case of "implementation first" design on the .NET > service side, which breaks interoperability. If the service > implementor > (whoever) had followed the recommended practice and used the WSDL > First > (tm) approach, then you'd be sipping tea right now, smiling at how > easy it all was to get things connected. > > Instead you're spelunking mailing lists looking for answers. > > -Dino > <Microsoft/> > > -----Original Message----- > From: Ralf Bust [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 30, 2005 4:27 AM > To: axis-user@ws.apache.org > Subject: Newbie Question / .NET SOAP Service / Dataset / any / > WSDL2Java > > Hi, > > i am currently developing a Client for an Airline Webservice. > So i have to connect to a .NET Webservice witch is using Microsoft datasets. > > The WSDL2Java is generating me wrong Code.(My Opinion) > > It seems that the generation of source code failes on: > <s:any namespace="http://tempuri.org/RAAvailabilityRequestDS.xsd"/> > > The Problem seems to be the type any witch referes to another xsd. > > I do not get errors, but the code generated does not look usable for me. > A short test with a .Net Framework brings up complete different > funktionality. > > Question: > Is Axis capable of using Datasets? > > The WSDL can be found: > http://services.radixx.com/RadixxFlights.asmx?WSDL > > Thx for help >
