On 01/04/2010 21:52, Clark wrote:
We recently started looking at moving from Tomcat 5.5.28 to 6.0.26 in
our development environment.
In the initial upgrade/testing of it, I have found the following that
gives me great concern.
Again, this is in a development sandbox, not a production
On 4/1/2010 5:23 PM, Pid wrote:
On 01/04/2010 21:52, Clark wrote:
The context.xml is in app-base/ROOT/META-INF
The server.xml, for both 5.5 and 6.0, is :
Server port=*8005* shutdown=*SHUTDOWN*
- # GlobalNamingResources
Resource name=*UserDatabase* auth=*Container*
On 01/04/2010 22:31, Clark wrote:
On 4/1/2010 5:23 PM, Pid wrote:
On 01/04/2010 21:52, Clark wrote:
The context.xml is in app-base/ROOT/META-INF
The server.xml, for both 5.5 and 6.0, is :
Server port=*8005* shutdown=*SHUTDOWN*
- # GlobalNamingResources
Resource name=*UserDatabase*
On 01/04/2010 21:52, Clark wrote:
We recently started looking at moving from Tomcat 5.5.28 to 6.0.26 in
our development environment.
In the initial upgrade/testing of it, I have found the following that
gives me great concern.
Again, this is in a development sandbox, not a production
From: Pid [mailto:p...@pidster.com]
Subject: Re: Significant change between 5.5 and 6.0 for Development
The Logger element isn't applicable in Tomcat 6.
Or 5.5, for that matter. It's always bad form to blindly copy configuration
from one level of Tomcat to another, but in this case
