Web application build process: Keep config files in WEB-INF/classes?

User-accessible config files are better stored outside of classes e.g. In WEB-INF/config I differentiate config files that site admins can touch (they are placed under WEB-INF ) and those, kind of 'static' ones, that are meant for developers/deployment configurators only (stuff like sql scripts, XML/XSLT templates, i18n etc).

User-accessible config files are better stored outside of /classes, e.g. In /WEB-INF/config. I differentiate config files that site admins can touch (they are placed under WEB-INF) and those, kind of 'static' ones, that are meant for developers/deployment configurators only (stuff like sql scripts, XML/XSLT templates, i18n etc). It is preferred practice to clean up WEB-INF/classes during builds - some classes get deleted/renamed, so are resource files.

Other config files, under WEB-INF, but not in /classes or /lib, have to be treated as upgradable resources: either replace old ones only when there is a new one, or use specifically designed upgrade classes to add missing config tags or lines. There are tricky situations, like log4j. Properties is sometimes stored into /classes root.

It is a bit of a different story how to properly handle it, but in most instances it falls under "delete all classes and copy everything anew".

1, Excellent answer. – Mikaveli Jun 14 at 8:52.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.