-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jesse,
On 10/12/2009 12:57 PM, Jesse Long wrote: > Unfortunately we have a very real use case for multiple instances on > one host, with different data paths. So, /etc/app.properties is not > usable, but /etc/app-<context path derived data>.properties might be > but virtual hosting would break. No way to identify unique host > consistently. I think that the previous suggestion of using JNDI to resolve either the path to a configuration file, or simply to determine the configuration itself (that is, have config values directly available through JNDI) is probably the right way to go: they can be specified by the server administrator, are context-specific, and do not require the developer to worry about them at all (except to read their values and act accordingly). > Also, I could use a path name derived from the temp directory name, > but nothing says the temp directory name will be consistent. For now > I will reluctantly use context parameters. Forget about the temp directory: the servlet spec is basically preventing that from being useful to you. Also, as someone pointed out, 'temporary' and 'persistent' are usually regarded as antonyms. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkrTbZkACgkQ9CaO5/Lv0PD9LwCfXjMj4Gg9pq3lZRkBpu2gHAfu IZ4An0pV3erpLLiLaKDer+yb7muMwOc3 =T9JR -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
