On 17/05/2010 16:56, peter_f...@blm.gov wrote: > > I'm a bit confused about what the deployOnStartup setting is supposed to > do, especially when it's set to "false". > > The basic question is, what is the purpose of this setting? It would appear > that if you set it to "false", then applications can only be started by > being hot-deployed, which seems rather odd but I suppose might be useful in > a development environment. By experiment I found that setting > autoDeploy=true and deployOnStartup=false, existing webapps are still > started but not until after Tomcat has already started (that is, the > applications get deployed a few seconds after Tomcat has started and is > listening, rather than during the usual startup sequence). I also found > that setting autoDeploy=false and deployOnStartup=false, no applications > will start (which is actually what I'd expect, even though it's pointless).
There are two attributes, both have obvious reasons for existing and each has a binary value. There doesn't need to be a specific use case for all 4 conditions. p > My guess would be that in a production setting you'd want > autoDeploy=false/deployOnStartup=true. > > There's a couple of places in documentation (online, and also in the > O'Reilly book) where it says you shouldn't have hot-deployment AND > deployOnStart enabled because it can result in applications being deployed > twice - and yet the default is that autoDeploy and deployOnStartup are both > true, which seems to contradict that, and in any case I've never seen this > happen. I'm plainly misunderstanding how these settings are supposed to > work. Perhaps someone here can clarify?
signature.asc
Description: OpenPGP digital signature
