Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 26764 invoked from network); 7 Mar 2005 15:16:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 7 Mar 2005 15:16:17 -0000 Received: (qmail 83231 invoked by uid 500); 7 Mar 2005 15:16:17 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 82693 invoked by uid 500); 7 Mar 2005 15:16:15 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 82680 invoked by uid 99); 7 Mar 2005 15:16:15 -0000 X-ASF-Spam-Status: No, hits=-10.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from minotaur.apache.org (HELO minotaur.apache.org) (209.237.227.194) by apache.org (qpsmtpd/0.28) with SMTP; Mon, 07 Mar 2005 07:16:15 -0800 Received: (qmail 26711 invoked from network); 7 Mar 2005 15:16:13 -0000 Received: from localhost.hyperreal.org (HELO ?127.0.0.1?) (127.0.0.1) by localhost.hyperreal.org with SMTP; 7 Mar 2005 15:16:13 -0000 Message-ID: <422C703C.20805@apache.org> Date: Mon, 07 Mar 2005 16:16:12 +0100 From: Juan Jose Pablos User-Agent: Debian Thunderbird 1.0 (X11/20050116) X-Accept-Language: en, es MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: JX generates weird NameSpace??? References: <20050225175402.GE12986@vision.anyware> In-Reply-To: <20050225175402.GE12986@vision.anyware> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: localhost.hyperreal.org 1.6.2 0/1000/N X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Jean-Baptiste Quenot wrote: > * oceatoon: > > >>Is anybody aware of such a thing as JX generating a weirds >>namespaces?? > > > Yes, and this has already been reported. > > But AFAICT it is *not* blocking. You may be facing another > problem without any relation to this namespace oddity. Do you have a bugid for this?