Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 28969 invoked from network); 20 Apr 2004 19:46:34 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 20 Apr 2004 19:46:34 -0000 Received: (qmail 96101 invoked by uid 500); 20 Apr 2004 19:44:05 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 96081 invoked by uid 500); 20 Apr 2004 19:44:05 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 96015 invoked from network); 20 Apr 2004 19:44:04 -0000 Received: from unknown (HELO exchange.sun.com) (192.18.33.10) by daedalus.apache.org with SMTP; 20 Apr 2004 19:44:04 -0000 Received: (qmail 23162 invoked from network); 20 Apr 2004 19:44:55 -0000 Received: from localhost (HELO nagoya) (127.0.0.1) by nagoya.betaversion.org with SMTP; 20 Apr 2004 19:44:55 -0000 Message-ID: <920388399.1082490295432.JavaMail.apache@nagoya> Date: Tue, 20 Apr 2004 12:44:55 -0700 (PDT) From: jira@apache.org To: axis-dev@ws.apache.org Subject: [jira] Updated: (AXIS-1326) ?WSDL emits elements in incorrect namespaces In-Reply-To: <1025503578.1082489996710.JavaMail.apache@nagoya> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N The following issue has been updated: Updater: Jonathan Anderson (mailto:anderson_jonathan@bah.com) Date: Tue, 20 Apr 2004 12:43 PM Changes: Attachment changed to axis12b_emitted.wsdl --------------------------------------------------------------------- For a full history of the issue, see: http://issues.apache.org/jira/browse/AXIS-1326?page=history --------------------------------------------------------------------- View the issue: http://issues.apache.org/jira/browse/AXIS-1326 Here is an overview of the issue: --------------------------------------------------------------------- Key: AXIS-1326 Summary: ?WSDL emits elements in incorrect namespaces Type: Bug Status: Unassigned Priority: Major Project: Axis Components: WSDL processing Assignee: Reporter: Jonathan Anderson Created: Tue, 20 Apr 2004 12:39 PM Updated: Tue, 20 Apr 2004 12:43 PM Environment: Axis 1.2 Beta, Windows XP Professional, Sun JDK/JRE 1.4.2_04 Description: In the attached WSDL, I do the following: BankService-DocLiteral.wsdl, target namespace: http://webservices.bah.com/examples/docliteral/bank ...which imports... BankService.xsd, target namespace: http://webservices.bah.com/examples/docliteral/bank ...which imports... BankTypes.xsd, target namespace: http://webservices.bah.com/examples/docliteral/bank/types Note that the Deposit element and DepositType type are defined in BankTypes.xsd, under the target namespace http://webservices.bah.com/examples/docliteral/bank/types. The DepositRequest element and DepositRequestType type are defined in BankService.xsd under the target namespace http://webservices.bah.com/examples/docliteral/bank, and DepositRequestType then *references* the Deposit element for inclusion inside of a sequence. At the end of the day I should have a "wrapper" element in namespace A with a child element in namespace B, a la: 100 100 The problem is then in the Axis 1.2 beta emitted WSDL (http://.../DocLiteralBankService?wsdl) for the service - it places the DepositType type in the correct namespace (http://webservices.bah.com/examples/docliteral/bank/types), but the Deposit element itself is in the wrong namespace (http://webservices.bah.com/examples/docliteral/bank). This results in the following: 100 100 Which of course the generated WSDL2Java service impl does not expect, so it throws: org.xml.sax.SAXException: Invalid element in com.bah.webservices.examples.docliteral.bank.DepositRequestType - Deposit --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira