Thanks for your help! When I did that, I got the following when I clicked on the service link from the listServices page:
- <error> <description>Unable to generate WSDL 1.1 for this service</description> <reason>If you wish Axis2 to automatically generate the WSDL 1.1, then please +set useOriginalwsdl as false in your services.xml</reason> </error> I would have thought it would just display the WSDL I gave it in the resources directory. Is that incorrect? Is there another location where it is expected? Thanks, Jennifer -----Original Message----- From: Raghu Upadhyayula [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 06, 2007 12:08 PM To: [email protected] Subject: RE: Configuration to use my WSDL rather than AXIS generated WSDL In the services.xml there is a parameter named " useOriginalwsdl", set that to true. Thanks Raghu -----Original Message----- From: Ford, Jennifer M. [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 06, 2007 9:55 AM To: [email protected] Subject: Configuration to use my WSDL rather than AXIS generated WSDL All: I am having some interoperability problems with a .NET client, and they've suggested that it's because of the changes that AXIS makes to my WSDL when the services are published. I'd like to make the services use the original WSDL, and it looks like there used to be a way to do that in the server-config.wsdd file. Is there a corollary to that for Axis 2? Thanks, Jennifer Ford --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
