RE: Why does 'WSDL2Java' change my WSDL!!

[tony . q . weddle]

Hi Morten,

The <service> element, in the WSDD file (deploy.wsdd or server-config.wsdd, which ends up holding all the deployed WSDD elements anyway) allows a sub element <wsdlFile> that specifies the location of the WSDL file for the service. If this is present, Axis, won't generate the WSDL.

If the WSDL accurately describes the service, your generated client code should work fine. I'm not sure what you mean by "does not match the service actually generated and deployed". Perhaps you could post a separate question for that, with the details.

Tony



Hi Tony,

- I guess not -  how do I do that?
Will it fit the Java-bindings generated? -As you can see from my
previous posting, it kind of appears as if the "WSDL2Java"-process
changes some of the types - I see a XMLSchema-string-type mutating to
something else.

I generated a web-service-client with the original WSDL used as input to
"WSDL2Java", but it does not match the service actually generated and
deployed.

The WSDD-file? The file "deploy.wsdd"?

**Please tell me more!**

Regards,
Morten Sabroe Mortensen