What are the consequences of putting shared web resources in the common
folder vs. the shared folder?
I'm not sure how to articulate the consequences of putting shared resources
in the common folder.
The following below is in the documentation, but is it enough to force
another QA cycle on
On 9 Jul 2008 at 11:57, Edward Song wrote:
What are the consequences of putting shared web resources in the common
folder vs. the
shared folder?
I´m not sure how to articulate the consequences of putting shared resources
in the common
folder.
The following below is in the
Steve Ochani wrote:
On 9 Jul 2008 at 11:57, Edward Song wrote:
What are the consequences of putting shared web resources in the common folder vs. the
shared folder?
I´m not sure how to articulate the consequences of putting shared resources in the common
folder.
The following below is
Date sent: Wed, 09 Jul 2008 12:42:34 -0400
From: David kerber [EMAIL PROTECTED]
Subject:Re: What are the consequences of putting shared web
resources in
the
common folder?
To: Tomcat Users List users@tomcat.apache.org
Send
Thanks guys for replying.
I should of stated that the shared resources were already in the common
folder and have been for quite a while.
It seems to work fine, however, I was looking at my catalina.properties and
the documentation and noticed that maybe the shared resources should be
moved to
If you look at the development of tomcat, you'll see tomcat 6.0.x
actually eliminated the split between shared and common putting all
shared and common jars in the /lib directory. I would guess it's
primarily because no one was using shared. With that in mind, I don't
see any benefit to
