The hardest problem with that is that you can't use context.getRealPath() to get the location of WEB-INF in an unpacked war config (per servlet spec). Honestly, classpath is usually the best solution.
-----Original Message----- From: Mathias Bogaert [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 10, 2003 6:55 PM To: [EMAIL PROTECTED] Subject: [OS-webwork] Configuration in /WEB-INF Guys, It seems like we are having a lot of problems with finding configuration files in the classpath etc. Also, I dislike putting configuration files other than .properties on the classpath. That's why I propose putting it all (components.xml, xwork.xml etc)under /WEB-INF directly (same as SiteMesh for example). +1 from me Mathias ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
