Andre,
On 10.9.2014 18:43, André Warnier wrote:
Otherwise, my customer sysadmins would have to unpack the WAR, edit
web.xml to insert their specific values, and re-pack the WAR. Which
they do not like to do either.
My customers also do not like a solution consisting in having these
parameters
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/10/2014 8:40 AM, sbre...@hotmail.com wrote:
Hello
We have a setup which compiles WAR applications once and deploys
them in various environments. Each environment has its own per
application Log4j configuration (WARN for production, DEBUG
Mark Eggers wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/10/2014 8:40 AM, sbre...@hotmail.com wrote:
Hello
We have a setup which compiles WAR applications once and deploys
them in various environments. Each environment has its own per
application Log4j configuration (WARN for
: Re: Context parameter override?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/10/2014 8:40 AM, sbre...@hotmail.com wrote:
Hello
We have a setup which compiles WAR applications once and deploys
them in various environments. Each environment has its own per
application Log4j
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/10/2014 9:43 AM, André Warnier wrote:
Mark Eggers wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
On 9/10/2014 8:40 AM, sbre...@hotmail.com wrote:
Hello
We have a setup which compiles WAR applications once and
deploys them in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/10/2014 11:55 AM, Mark Eggers wrote:
Context ctx = new InitialContext(); Integer maxExemptions =
ctx.lookup(java:comp/env/maxExemptions);
Try / catch and other issues are left as exercises for the reader.
Urp, at least get the casting
2014 09:03:59 -0700 From:
its_toas...@yahoo.com.INVALID To: users@tomcat.apache.org
Subject: Re: Context parameter override?
On 9/10/2014 8:40 AM, sbre...@hotmail.com wrote:
Hello
We have a setup which compiles WAR applications once and
deploys them in various environments. Each
2014-09-10 21:52 GMT+04:00 sbre...@hotmail.com:
(...)
What puzzles me is the Context / Parameter feature of Tomcat. (context-param
from Java is clear.) There are at least 3 locations to define Tomcat level
parameters:
- server.xml / Host (1)
- webapps / ... / context.xml (2)
-
logs related to my parameter declaration. I shall look into the
Tomcat code to understand this.
Date: Thu, 11 Sep 2014 00:20:19 +0400
Subject: Re: Context parameter override?
From: knst.koli...@gmail.com
To: users@tomcat.apache.org
2014-09-10 21:52 GMT+04:00 sbre...@hotmail.com
doesn't have a robust API.
. . . just my two cents
/mde/
Date: Thu, 11 Sep 2014 00:20:19 +0400 Subject: Re: Context
parameter override? From: knst.koli...@gmail.com To:
users@tomcat.apache.org
2014-09-10 21:52 GMT+04:00 sbre...@hotmail.com:
(...)
What puzzles me is the Context
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 9/10/14 6:45 PM, Mark Eggers wrote:
Responses inline.
On 9/10/2014 1:33 PM, sbre...@hotmail.com wrote:
I am pretty sure I tried option 3 and Log4j initialization did
ignore my log4jConfigLocation setting in conf/.../myapp.xml.
Oh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris,
On 9/10/2014 4:48 PM, Christopher Schultz wrote:
Mark,
On 9/10/14 6:45 PM, Mark Eggers wrote:
Responses inline.
On 9/10/2014 1:33 PM, sbre...@hotmail.com wrote:
I am pretty sure I tried option 3 and Log4j initialization did
ignore
it?
Date: Wed, 10 Sep 2014 16:58:08 -0700
From: its_toas...@yahoo.com.INVALID
To: users@tomcat.apache.org
Subject: Re: Context parameter override?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris,
On 9/10/2014 4:48 PM, Christopher Schultz wrote:
Mark,
On 9/10/14 6:45 PM, Mark
13 matches
Mail list logo
