Thanks for your help guys. I've never really considered modifying a .war
outside of the normal build process an acceptable thing to do. But, it
appears that is the recommended approach from the Tomcat community so I'll
work with my middleware organization to see if we can get something like
that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike,
On 1/14/2010 6:45 PM, youngm wrote:
> * It would seem that the change tracking of a process like that above would
> be very difficult. It would be hard to answer questions like "What patches
> have I applied to these 20 applications in producti
On 14/01/2010 23:45, youngm wrote:
* It would seem that the change tracking of a process like that above would
be very difficult. It would be hard to answer questions like "What patches
have I applied to these 20 applications in production?" If there were
simply a folder with the patches right
On 14/01/2010 23:45, youngm wrote:
>> Won't help. The servlet spec requires that classes in the web
>> application take priority.
>
> The only quote I was able to find from the servlet spec was:
>
> "It is recommended also that the application class loader be
> implemented so that classes and res
> From: youngm [mailto:you...@gmail.com]
> Subject: Re: Classloader between Web application and system loader
>
> * If I'm administering an environment with 20-30 tomcat apps
> all of which require the new database driver this is a rather
> more difficult process for mi
>Very bad idea. Search the archives for a long list of things that go
>wrong when you start changing the class path. Not to mention that would
>make the new driver visible to all web applications not just the web app
>that needed the new jar file. And you'd need to restart Tomcat for the
>changes
On 14/01/2010 22:19, youngm wrote:
> I personally don't like any of the options.
If you articulated your concerns, then we might be able to show you
solutions to them.
> Here are a couple of solutions
> that I might like a little more. I'd be curious if anyone likes any of
> these.
>
> 1. modif
Ok, so to sum up this is what I've gathered.
Here is my hypothetical situation. I have a .war running in production.
This war embeds an oracle driver in its WEB-INF/lib. Middleware discovers
that there is a security vulnerability in this oracle driver and need to do
an emergency upgrade of the
2010/1/14 youngm :
>
>
>>Put expanded classes into WEB-INF/classes.
>>Likewise, in CATALINA_BASE/lib
>
> So CATALINA_BASE/lib jars and classes are used before the application
> (WEB-INF/lib and /classes)?
>
No, they are not.
WEB-INF is used before CATALINA_BASE, but actually that is a more
compli
> From: Pid [mailto:p...@pidster.com]
> Subject: Re: Classloader between Web application and system loader
>
> You might get away with adding individual classes to the classloader
> tree, but multiple jars containing the same class is likely to cause
> problems. In fact, I&#
On 14/01/2010 02:40, youngm wrote:
Put expanded classes into WEB-INF/classes.
Likewise, in CATALINA_BASE/lib
So CATALINA_BASE/lib jars and classes are used before the application
(WEB-INF/lib and /classes)?
http://tomcat.apache.org/tomcat-6.0-doc/class-loader-howto.html under Class
Loader D
>Put expanded classes into WEB-INF/classes.
>Likewise, in CATALINA_BASE/lib
So CATALINA_BASE/lib jars and classes are used before the application
(WEB-INF/lib and /classes)?
http://tomcat.apache.org/tomcat-6.0-doc/class-loader-howto.html under Class
Loader Definitions seems to indicate otherwis
2010/1/14 Rob S. :
> Konstantin, do you have to modify one of the loaders in catalina.properties
> to check in CATALINA_BASE/lib? Or it does that automagically?
>
In 6.0.20 it is by default:
What comes first takes priority in an URLClassLoader.
common.loader=${catalina.home}/lib,${catalina.home}
Konstantin, do you have to modify one of the loaders in catalina.properties
to check in CATALINA_BASE/lib? Or it does that automagically?
On Wed, Jan 13, 2010 at 5:21 PM, Konstantin Kolinko
wrote:
> 2010/1/14 youngm :
> >
> > I am designing my production Tomcat 6 system and would like to have a
2010/1/14 youngm :
>
> I am designing my production Tomcat 6 system and would like to have a
> classloader where I can put emergency "patch" jars (e.g. database drivers,
> etc) and configuration (e.g. tweaked spring config).
>
> These artifacts would need to be loaded in a classloader between the S
15 matches
Mail list logo
