Return-Path: Delivered-To: apmail-incubator-cxf-issues-archive@locus.apache.org Received: (qmail 656 invoked from network); 4 Sep 2007 20:27:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Sep 2007 20:27:17 -0000 Received: (qmail 4851 invoked by uid 500); 4 Sep 2007 20:27:11 -0000 Delivered-To: apmail-incubator-cxf-issues-archive@incubator.apache.org Received: (qmail 4839 invoked by uid 500); 4 Sep 2007 20:27:11 -0000 Mailing-List: contact cxf-issues-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cxf-dev@incubator.apache.org Delivered-To: mailing list cxf-issues@incubator.apache.org Received: (qmail 4830 invoked by uid 99); 4 Sep 2007 20:27:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Sep 2007 13:27:11 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Sep 2007 20:27:05 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 42702714209 for ; Tue, 4 Sep 2007 13:26:45 -0700 (PDT) Message-ID: <13149698.1188937605268.JavaMail.jira@brutus> Date: Tue, 4 Sep 2007 13:26:45 -0700 (PDT) From: "Daniel Kulp (JIRA)" To: cxf-issues@incubator.apache.org Subject: [jira] Commented: (CXF-959) Incorrect namespace configuration when generating wsdl In-Reply-To: <29959103.1188581718755.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/CXF-959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524861 ] Daniel Kulp commented on CXF-959: --------------------------------- Right. Basically, the path right now looks like: 1) Build up JDOM version of the schema 2) Use DOMOutputter to convert JDOM to W3C DOM 3) Create XmlSchema object from W3C DOM. In step 3, XmlSchema uses the Attribute nodes that are in the in the "http://www.w3.org/XML/1998/namespace" namespace to find the namespace prefixes to populate the default NamespaceContext. However, due to the JDOM bug, it doesn't find any so the default NamespaceContext is empty. Your fix works around that by providing a valid NamespaceContext. > Incorrect namespace configuration when generating wsdl > ------------------------------------------------------ > > Key: CXF-959 > URL: https://issues.apache.org/jira/browse/CXF-959 > Project: CXF > Issue Type: Bug > Environment: Using CXF 2.0.1 > Reporter: Brian Sawyer > Assignee: Daniel Kulp > Attachments: cxf-959.jar, cxf-959.patch, name-service.jar > > > Following is an example service and its generated wsdl: > import com.basistech.stuff.Name; > @WebService(name="NameService", targetNamespace="urn:com.basistech.service") > public interface NameService { > @WebMethod > public abstract List listAvailableNames(); > } > > > > > > > > > > > > > > > > ArrayOfName is said to contain an element of type ns1:Name. However, ns1 is set to "http://nameService.basistech.com" when Name is actually located in the "http://stuff.basistech.com" namespace. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.