Hi Giacomo, Some hints about the relationships : - APACHE SOAP is a follow on of the IBM SOAP4J project (http://www.alphaworks.ibm.com/tech/soap4j) - AXIS is a rewrite of APACHE SOAP (http://xml.apache.org/axis/faq.html#faq1) - IBM WSTK uses AXIS as its runtime engine (http://www-3.ibm.com/software/solutions/webservices/wstk-info.html)
As far as interoperability issues are concerned, I assume from the above that WSTK and AXIS should have a very similar behaviors. There is an interop page on axis web site (http://www.apache.org/~rubys/ApacheClientInterop.html) so you can have a look at which data structure are working fine with M$.net. Some of the active commiters are working at IBM (http://xml.apache.org/axis/who.html), so you can be sure of the involvement of IBM in the AXIS project. Hope this helps, Denis > ----- Mensaje Original ----- > Remitente: Giacomo Fiorentini <[EMAIL PROTECTED]> > Fecha: Jueves, Julio 4, 2002 10:52 am > Asunto: SOAP -- .net interoperability -- questions > > > > > Hi all, > > I'm new on this mailing list. I have the following question: > > > > what are the relationship, differences, prospectives, expectations > > of the > > following SOAP implementations/libraries/tools: > > > > Java Web Service Developer Pack 1.0 > > Apache SOAP 2.3.1 > > Apache Axis beta 2 > > Web Service Toolkit from IBM > > > > I know that this was a strange question, but we have to decide the > > besttools/library for new projects, that will have to interoperate > > withMicrosoft .net ws. > > > > I tried the Axis beta 2, with interoperability with .net (to and > > from), and > > I didn't found particular problems (I was limited with base data > > types), but > > I wonder what can be the problems on mappings complex structures > > like .net > > DataSet. > > > > Apache SOAP and WSDP are very useful for deep programming with > > SOAP, but are > > not very easy to program. I found that the manual generation of > > WSDL files > > is not very useful for designing large projects: it's an added > > complexitynot necessary. > > > > I think that the simple meccanismo on axis, that provides automatic > > generation of WSDL files simply adding the ?wsdl is very very > > useful, and > > it's very similar to the .net ws behaviour. > > > > For completeness, I'm not jet tried the WSTK. > > > > > > Any comments, suggestions are welcome. > > > > Thanks. > > > > > > Giacomo Fiorentini > > > > > >
