First rule of SOA: Web services are not the same as distributed objects. In order to implement loosely coupled systems, you must create a clean layer of abstraction between your service interface and your service implementation. If you generate your interface from the implementation, you will build tightly coupled systems that will invariably encounter interoperability issues.
If you want to build loosely coupled systems, then you should start your development effort by defining the format of the messages you will exchange -- XML schema. The reason we have java2wsdl is that lots of early efforts focused on using SOAP and WSDL to implement an XML-based distributed object system -- all the tools focused on generating RPC/encoded services. We've since learned that RPC/encoded causes some nasty interoperability issues. The challenge with java2wsdl is that there's an impedance mismatch between Java and XML type systems, so it's difficult to fully automate the mapping between Java and XML types. It's okay to use java2wsdl as a shortcut to build a WSDL template, but you should always edit the generated XML schema definitions to make sure that your message formats are okay. Anne -----Original Message----- From: WAJSBERG Julien RD-BIZZ [mailto:[EMAIL PROTECTED] Sent: Friday, September 24, 2004 3:35 AM To: [EMAIL PROTECTED] Subject: Re: Axis and .NET interoperability - Arrays Ellecer Valencia a �crit : >(i'll probably be told to create WSDL first... but if so, why then do >we have java2wsdl?) > > You can generate a first draft with java2wsdl, modify it according to your needs, and use wsdl2java afterwards :) -- Julien
