, 2001 5:01 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Setting properties outside of the WAR
Hi Ritchie (and anyone else interested)
Something else occurred to me after sending this email,
and reading an unrelated email from Craig.
Craig was talking about being able to run a webapp direct
from a WAR
aig R. McClanahan [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, January 02, 2001 10:10 PM
To: [EMAIL PROTECTED]
Subject: Re: Setting properties outside of the WAR
Ritchie Young wrote:
Thanks for the response but that wasn't quite what I was getting at.
The idea was that there should be some
Regards,
Simon
-Original Message-
From: Craig R. McClanahan [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, January 02, 2001 10:10 PM
To: [EMAIL PROTECTED]
Subject: Re: Setting properties outside of the WAR
Ritchie Young wrote:
Thanks for the response but that wasn't qui
IL PROTECTED]]
Sent: Wednesday, January 03, 2001 4:30 PM
To: [EMAIL PROTECTED]
Subject: Re: Setting properties outside of the WAR
Oh good, it's not just me.
Thanks, I would appreciate it if you did forward me a copy of that script.
Cheers
Ritchie
- Original Message -
F
Perhaps where this is going is a WebApp configurator that knew how to
parse XML's , and could display the properties as a
administrator-friendly menu, rather than a grisly collection of XML
tags. The application might also be able to save a backup copy of
configuration, and perhaps patch an older
Kitching Simon wrote:
I think that this whole issue (specifying configuration parameters
to web applications) needs some serious thought - possibly
at the level of the servlet spec development group, even.
The best place to address your suggestions and comments in this regard is
"[EMAIL
server's I've seen offer some sort of "deployment tool" that
lets you perform
customizations like this as you deploy an application.
Off the top of my head, it seems that the right way to do it
would be to specify a properties extension mechanism with
more expressiveness than the simple
Thanks for the response but that wasn't quite what I was getting at.
The idea was that there should be some easy way for an administrator to set
a property for the application. It just strikes me that the TOMCAT_OPTIONS
variable is a slightly cumbersome way especially when there start to be a
