On Fri, Aug 26, 2005 at 02:16:26AM +0800, Patrick Lacson wrote: : I know that's typically where they go, but if the file is inside the : .war, how is the file going to be configured by the sysadming folks?
Webapps are meant to be fairly standalone. If you require that one be configured after it has been compiled, you really have two options: 1/ give it to the sysadmins in exploded-dir format so they can tweak the files, then just run the app as such 2/ create some resource outside of the app (database, file) that the app knows to load on startup. The downside to #2 is that it still requires your app to have some knowledge of the filesystem outside of itself. That inhibits portability, not to mention running separate instances of the app (with separate configurations, that is). Furthermore, to be completely portable across containers (though not necessarily operating systems) your app must operate on the fully-qualified path to the external file. There's no such idea as a "relative file location" when it comes to webapps. What would be in this external config file? -QM -- software -- http://www.brandxdev.net/ tech news -- http://www.RoarNetworX.com/ code scan -- http://www.JxRef.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
