tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From br1 <myrealbr...@myrealbox.com>
Subject RE: Convenient web application configuration.
Date Thu, 30 Oct 2008 22:25:37 GMT

Hi,


Caldarale, Charles R wrote:
> 
>> From: br1 [mailto:myrealbruno@myrealbox.com]
>> Subject: Re: Convenient web application configuration.
>>
>> The easiest way is to place Context and the different
>> Resource elements into each Tomcat's server.xml file.
> 
> Certainly not "easiest" by any definition of the term that I'm familiar
> with, especially in a production environment. 
> 

It probably depends on requirements. I am familiar calling it the "easiest"
and I manage production environments.


Caldarale, Charles R wrote:
> 
> 1) Restart of Tomcat (not just the webapp) required when *any* changes are
> needed.
> 

It just takes a few seconds, and *any* change is done first in the
development environment. When the test environment is happy, the production
one is just restarted once.
Also, do you mean "deploy a webapp under Windows without restarting Tomcat"?



Caldarale, Charles R wrote:
> 
> 2) Sysadmins don't like app developers mucking with server configurations.
> 


Absolutely! I did not mean this at all. 
I mean that some sysadmins are happy to waste their time to fix these
details themselves for exactly this reason.
And they don't like app developers deciding the app path, nor they like app
developers decide where their log files should go or where, for instance, a
full text index should stay. The list is long, and no one forgot database
connections.


Caldarale, Charles R wrote:
> 
> 3) Doesn't bundle the webapp-specific configuration with the webapp.
> 


Making the webapp point to a development or production database is not
specific to the webapp at all. It is specific to the environment (the
"context") that the webapp is running on. Same applies to other resources as
I mentioned above. 
Another reason you want to do it: you want connection pooling at the Tomcat
instance level, and you use a global JNDI resource, that means "edit the
server.xml". (Thunder here)



Caldarale, Charles R wrote:
> 
> 4) Error prone due to the manual editing required.
> 
>  - Chuck
> 


Just like any other file the sysadmin edits.. also see point (1).
In no case I was suggesting an app developer to edit files, other than the
development environment.

br1

-- 
View this message in context: http://www.nabble.com/Convenient-web-application-configuration.-tp20244034p20256710.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message