Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 33796 invoked from network); 27 Mar 2006 02:59:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 27 Mar 2006 02:59:34 -0000 Received: (qmail 15876 invoked by uid 500); 27 Mar 2006 02:59:27 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 15836 invoked by uid 500); 27 Mar 2006 02:59:26 -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: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 15823 invoked by uid 99); 27 Mar 2006 02:59:26 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 26 Mar 2006 18:59:26 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [206.123.75.163] (HELO sosnoski.com) (206.123.75.163) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 26 Mar 2006 18:59:25 -0800 Received: from [192.168.0.2] (222-152-132-196.jetstream.xtra.co.nz [222.152.132.196]) (authenticated bits=0) by sosnoski.com (8.12.10/8.12.10) with ESMTP id k2R2x28C021211 for ; Sun, 26 Mar 2006 21:59:03 -0500 Message-ID: <442754F5.9030809@sosnoski.com> Date: Mon, 27 Mar 2006 14:59:01 +1200 From: Dennis Sosnoski User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050322) X-Accept-Language: en-us, en MIME-Version: 1.0 To: axis dev Subject: [Axis2] Schema with no targetNamespace rejected Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N The resolution of http://issues.apache.org/jira/browse/AXIS2-67 was to add a check that the schema definition within a WSDL defines a targetNamespace. What is the justification for this? AFAIK it's perfectly valid to have a nonamespace schema in a WSDL, even though it's recommended that you use namespaces. If XMLBeans requires a targetNamespace (what appears to be the original justification given in the problem report), then the XMLBeans code generation extension should perform this check and throw an error. Can someone supply a justification of this decision? - Dennis -- Dennis M. Sosnoski SOA, Web Services, and XML Training and Consulting http://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA +1-425-296-6194 - Wellington, NZ +64-4-298-6117