Are you using Doc/Literal or RPC/Encoded? If you are using Doc/Literal, then the namespace comes from the targetNamespace of the <schema> definition that describes the <getWSResponse> element in the <types> section.
If you are using RPC/Encoded, then the namespace comes from the namespace attribute in the WSDL binding/operation/output definition. To specify a specific namespace, you can add a namespace declaration in the WSDD. See http://nagoya.apache.org/wiki/apachewiki.cgi?AxisProjectPages/Namespaces. In any case, I think this is a bug. Per the WS-I BP, the child element of the SOAP Body must be namespace qualified: 4.1.13 SOAP Body and Namespaces The use of unqualified element names may cause naming conflicts, therefore qualified names must be used for the children of soap:Body. R1014 The children of the soap:Body element in a MESSAGE MUST be namespace qualified. Please file it as a bug. Anne -----Original Message----- From: Satrusalya, Prassana [mailto:[EMAIL PROTECTED] Sent: Friday, May 07, 2004 9:38 AM To: '[EMAIL PROTECTED]' Subject: WSDL autogeneration - xmlns="" in service response In my response axis sends back the response the following way. Notice the ' xmlns="" ' . .NET does not like it. My WSDL is generated on the fly and I am using Simple types. Any idea how to avoid this. <?xml version="1.0" encoding="UTF-8" ?> - <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> - <soapenv:Body> - <getWSResponse xmlns=""> <getWSReturn>kk</getWSReturn> </getWSResponse> </soapenv:Body> </soapenv:Envelope> Thanks, Kumar ---------------------------------------------------------------------------- -- Notice: This e-mail message, together with any attachments, contains information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station, New Jersey, USA 08889), and/or its affiliates (which may be known outside the United States as Merck Frosst, Merck Sharp & Dohme or MSD and in Japan as Banyu) that may be confidential, proprietary copyrighted and/or legally privileged. It is intended solely for the use of the individual or entity named on this message. If you are not the intended recipient, and have received this message in error, please notify us immediately by reply e-mail and then delete it from your system. ---------------------------------------------------------------------------- --
