Anne is 100% correct in my opinion (which is very often the case). You need to worry about WSDL and XSD when designing a contract.
I wish it was easy to mix modes though. I want to provide an WSDL down to binding then wsdl:import that into a generated "root WSDL" so the runtime provides the <wsdl:service> element and most importantly the soap:address value. The biggest PITA with WSDL first (after writing the WSDL/XSD) is keeping the endpoint address right. Allowing the runtime to manage that part is so much easier and doesn't impact the contract in a semantically significant way. Jim Murphy Mindreef, Inc. On 3/15/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > My point is -- don't generate a new WSDL. Use your old WSDL and generate a > new service from the original WSDL, and tell Axis to use the original WSDL > rather than auto-generating a new one (specify the wsdlFile in the WSDD). > > > Anne > > On 3/14/06, Siddhartha Subramanian > <[EMAIL PROTECTED]> wrote: > > > > > > > > > > Well I understand the changes and the need for them, but once my WSDL has > been published and the clients using it expect the client side to be in a > certain way (packaging wise, namespaces etc.) but with 1.3 I cannot say > regenerate the WSDL and publish it because what you are suggesting of > generating the code from the new WSDL does not produce the same client side > stubs expected. So we have to manipulate the WSDL by hand to conform to the > namespacing and there by producing the old packaging structure. > > > > ________________________________ > > > > > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, March 14, 2006 6:32 PM > > To: [email protected] > > Subject: Re: WSDL2Java and Java2WSDL > > > > > > > > > > One way to ensure that your WSDLs are the same is to generate your code > from the WSDL rather than vice versa. > > > > But most likely, your Axis 1.1 WSDL will produce interoperability errors. > If they contain arrays, they probably have errors. Axis 1.2 and later > releases added support for JAX-RPC 1.1 and the WS-I Basic Profile, and they > dramatically improved support for document/literal. Lots and lots of changes > were made in dealing with arrays. > > > > Anne > > > > > > On 3/14/06, Siddhartha Subramanian < > [EMAIL PROTECTED]> wrote: > > > > I have been trying something using 1.1 final and 1.3 WSDL2Java and > > Java2WSDL produces different types of WSDLs with the Java2WSDL and > > WSDL2Java produces different java packaging with the different versions. > > > > Can anyone tell me why the change and what changed between 1.1 and 1.3? > > I believe there is no way to generate the same WSDL as the 1.1 final > > produced with the 1.3 version. Am I wrong with this statement? > > > > > >
