Return-Path: 
 <dev-return-76018-apmail-geronimo-dev-archive=geronimo.apache.org@geronimo.apache.org>
Delivered-To: apmail-geronimo-dev-archive@www.apache.org
Received: (qmail 16344 invoked from network); 27 Aug 2009 08:15:16 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 27 Aug 2009 08:15:16 -0000
Received: (qmail 60997 invoked by uid 500); 27 Aug 2009 08:15:16 -0000
Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org
Received: (qmail 60897 invoked by uid 500); 27 Aug 2009 08:15:16 -0000
Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@geronimo.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@geronimo.apache.org>
List-Post: <mailto:dev@geronimo.apache.org>
Reply-To: dev@geronimo.apache.org
List-Id: <dev.geronimo.apache.org>
Delivered-To: mailing list dev@geronimo.apache.org
Received: (qmail 60889 invoked by uid 99); 27 Aug 2009 08:15:16 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Aug 2009 08:15:16 +0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=SPF_PASS,UNPARSEABLE_RELAY
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: local policy)
Received: from [98.136.44.59] (HELO smtp104.prem.mail.sp1.yahoo.com)
 (98.136.44.59)
    by apache.org (qpsmtpd/0.29) with SMTP; Thu, 27 Aug 2009 08:15:06 +0000
Received: (qmail 91241 invoked from network); 27 Aug 2009 08:14:44 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:Message-Id:From:To:In-Reply-To:Content-Type:Content-Transfer-Encoding:Mime-Version:Subject:Date:References:X-Mailer;
  b=O9iP+IRJMTE8WfNpT3koBNzKmB+wORl19awW6UjcTluAvrTURInrq6tOjrv9HZEoxwhC89bUh9LurpeFCTcD4rlq7eb9A+zibdyWfJTnv7OnPUhgWnjjgFgdfxwUM0lquExu2a2wYo99/IY/QfztfFwHYb6UiyZ2KXyMcQVz+OM=
  ;
Received: from 076-076-148-215.pdx.net (david_jencks@76.76.148.215 with plain)
        by smtp104.prem.mail.sp1.yahoo.com with SMTP;
 27 Aug 2009 01:14:43 -0700 PDT
X-Yahoo-SMTP: .9oIUzyswBANsYgUm_5uPui0skTnzGJXJQ--
X-YMail-OSG: 
 xs_G.VkVM1nQQZ60OfuSXLaX4ATrlYydZJIikLyIjrrMG1qn8W3.C8Fn4_1.yLJRyUNRBmYpFes6yvmwlSfwsRU_kC3PPm1Z1KK_AdCmqAWZz69lJnlKjR5DHD.XblJReqvIqGSeWKuMf3SnyDduePAm3w51u.DUgmhVfMaOCNKlknGNhYgvYkrAAz0rEQ2geHExxc7Q94sExZvp5gVc_5aSjmGRqHIaqU_ub4vDtDzc6w7vVLc-
X-Yahoo-Newman-Property: ymail-3
Message-Id: <1EB233C1-DCBF-4576-9372-E82F8D16C015@yahoo.com>
From: David Jencks <david_jencks@yahoo.com>
To: dev@geronimo.apache.org
In-Reply-To: <45f744e40908262330o796e1da4y583a07ccd91eb23a@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: Disable Tomcat JNDI
Date: Thu, 27 Aug 2009 01:14:42 -0700
References: <45f744e40908262330o796e1da4y583a07ccd91eb23a@mail.gmail.com>
X-Mailer: Apple Mail (2.936)
X-Virus-Checked: Checked by ClamAV on apache.org

I think this is a good idea if it doesn't break stuff.  I think I  
recall having some difficulty figuring out how to completely disable  
tomcat jndi.  Perhaps you will be able to figure out how :-)

thanks
david jencks

On Aug 26, 2009, at 11:30 PM, Ivan wrote:

> Hi,
>    I found some configurations like
>    --->
>   <GlobalNamingResources>
>         <!-- Editable user database that can also be used by
>              UserDatabaseRealm to authenticate users
>         -->
>         <Resource name="UserDatabase" auth="Container"
>                   type="org.apache.catalina.UserDatabase"
>                   description="User database that can be updated and  
> saved"
>                    
> factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
>                   pathname="conf/tomcat-users.xml"/>
>     </GlobalNamingResources>
>   <---
>   in the var/catalina/server.xml file, since we use xbean-naming as  
> our JNDI implementation, we should disable Tomcat's own JNDI. While  
> disabling Tomcat's JNDI, we should not allow the users to define  
> those settings in the server.xml. I think, we need to remove  
> GlbalNamingResources fragment from the server.xml and add some  
> comments, which tell the user never define those resources in the  
> server.xml.
> Any comment ?
>
> -- 
> Ivan