Return-Path: Delivered-To: apmail-xml-axis-user-archive@xml.apache.org Received: (qmail 82770 invoked by uid 500); 27 Aug 2002 14:32:53 -0000 Mailing-List: contact axis-user-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-user@xml.apache.org Received: (qmail 82753 invoked from network); 27 Aug 2002 14:32:53 -0000 Message-ID: <3D6B8D90.8BA606F3@watson.ibm.com> Date: Tue, 27 Aug 2002 10:32:48 -0400 From: Rania Khalaf Reply-To: rkhalaf@watson.ibm.com Organization: IBM X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: axis-user@xml.apache.org, axis-dev@xml.apache.org Subject: Bug in WSDL generation Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Status: O X-Status: X-Keywords: If you try to type map something in the xsd namespaces, the WSDL generation puts the name of your class (namespace is the package name, and local part is the class name) as the QName in the generated WSDL. Example if in my WSDL I map: xsd:date (where xmlns:xsd="http://www.w3.org/2001/XMLSchema")to my.special.Date using mySpecializedSer/DeserFactory then the WSDL says that that the type is of type ns:Date where xmlns:ns="http://special.my" but if I change the xsd namespace to http://something/not/schema then it does the right thing in the WSDL. In both cases the service/client interactions are fine so the problem is confined to the WSDL generation and does not extend to the ser/deser etc mappings.