Have we done a little test to make sure that removing/disabling Tomcat's JNDI does not break things? If everything looks good, it certainly makes good sense to do that. :-)
-Jack On Thu, Aug 27, 2009 at 2:30 PM, Ivan <[email protected]> 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 >
