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
