|
Can that be done? If so how can you specify that in the deploy.wsdd? Regards, Subir From: Anne Thomas
Manes [mailto:[EMAIL PROTECTED] 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). 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]] One way to ensure that your WSDLs are the same is to
generate your code from the WSDL rather than vice versa. On
3/14/06, Siddhartha Subramanian
<
[EMAIL PROTECTED]> wrote: I
have been trying something using 1.1 final and 1.3 WSDL2Java and
|
- RE: WSDL2Java and Java2WSDL subir.sasikumar
- Re: WSDL2Java and Java2WSDL Anne Thomas Manes
- Re: WSDL2Java and Java2WSDL Jim Murphy
