How many web apps do you have?
Put the jar in shared, and you get to restart them all anyway...on
each shared jar update.
I am sure your users will love that. ;-)
Larry
On 6/15/05, teknokrat <[EMAIL PROTECTED]> wrote:
> delbd wrote:
> > Then put those libs in WEB-INF/lib too
> And if we need
delbd wrote:
Then put those libs in WEB-INF/lib too
Le Mardi 14 Juin 2005 14:31, teknokrat a écrit :
Charl Gerber wrote:
When do you share jars (struts, log4j, jstl, etc) for
webapps in the common/lib directory and when does each
app need its own "copy" of the jars?
Log4j we've found by tra
Bottom line is that the only libraries you should put in shared/lib
are ones that you know are stable and won't be changing much, if at
all (can anybody really know this?). Every application that depends
on a shared library gets impacted when you upgrade the shared library.
If there are several d
> ==
> Date: Tue, 14 Jun 2005 11:43:04 +0100 (BST)
> From: Charl Gerber <[EMAIL PROTECTED]>
> To: Tomcat Users List
> Subject: RE: [Q] when to share jars
> ==
>
> yep, shared/lib.
>
> I suspect struts also ne
Then put those libs in WEB-INF/lib too
Le Mardi 14 Juin 2005 14:31, teknokrat a écrit :
> Charl Gerber wrote:
> > When do you share jars (struts, log4j, jstl, etc) for
> > webapps in the common/lib directory and when does each
> > app need its own "copy" of the jars?
> >
> > Log4j we've found by t
Charl Gerber wrote:
When do you share jars (struts, log4j, jstl, etc) for
webapps in the common/lib directory and when does each
app need its own "copy" of the jars?
Log4j we've found by trail and error is better to have
a jar per webapp, as the loggers seems to overwrite
each other, but which c
Amen brother!
Sharing jars between web apps is just a Bad Idea (tm).
Disk is cheap, and so is the time required to copy a jar.
...unless you are an ISP with 1000+ web apps running on a sinlge box,
then it *might* be OK, but even then, I would stop and think very
carefully before doing it.
Lar
Tim Funk wrote:
Never. I share jars. I wish I hadn't.
When you upgrade JSTL, struts, etc - all get the upgrade for free -
but that means ultra stable apps which haven't been touched in years
may "magically break".
You're absolutely right Tim. If it works, don't fix it. And there is
nothin
The best place to search for this info is in the library website. You found
the problem of log4j by trail / error? if you had read the log4j doc, it's
written explicitly, do not put log4j in the shared lib of your container or
you won't be able to have a different config per webapp.
For struts,
I think so. But IIRC, if you have a log4j in common/lib and WEB-INF/lib - the
WEB-INF/lib will be used for that webapp. So you can place logging in a
different file for that webapp and class.
-Tim
Charl Gerber wrote:
If you share log4j, wouldn't it mean that if two
web-apps both use eg "com
If you share log4j, wouldn't it mean that if two
web-apps both use eg "com.foo.Bar", they cannot be
configured to log to different logfiles and that the
com.foo.Bar logger (with appenders) is shared between
webapps?
--- Tim Funk <[EMAIL PROTECTED]> wrote:
> Never. I share jars. I wish I hadn't.
Never. I share jars. I wish I hadn't.
When you upgrade JSTL, struts, etc - all get the upgrade for free - but that
means ultra stable apps which haven't been touched in years may "magically
break".
[Exception - log4j ... I like have a common/lib log4j]
-Tim
Charl Gerber wrote:
When do you
yep, shared/lib.
I suspect struts also needs to be in every webapp, but
its gets tricky when you consider all the jars struts
require, eg commons-related stuff.
--- "Dale, Matt" <[EMAIL PROTECTED]> wrote:
>
> They need to be in common/lib when they need to be
> accessed by tomcat itself as wel
They need to be in common/lib when they need to be accessed by tomcat itself as
well as the webapps. shared/lib would just be the webapps. I don't know about
struts and jstl but you'd more than likely need a log4j in each webapp to get
seperate webapp logging.
Ta
Matt
-Original Message---
14 matches
Mail list logo
