I know the basic directory structure under Tomcat is as follows :
webapps/BeerV1/ with WEB-INF/classes directly beneath that.
Actually, then, you DON'T know the basic directory structure under Tomcat. Tomcat employs (by default), the directory TOMCAT_HOME/webapps. Within that directory you can deploy J2EE web applications. At that point, however, you're no longer "Tomcat directory structure", you're J2EE WAR structure. Each WAR appears as a file and/or directory in Tomcat_HOME/webapps, and the structure from that point downwards is set by the J2EE standard, not by Tomcat. Within the webapps directory, if a file ending in ".war" and a directory (no extension) have the same name, Tomcat will deploy the directory version of the app and ignore the WAR file (even if it's newer than the directory version). That's assuming that you're running Tomcat with the factory options and that you didn't define an explicit Tomcat Context.
Within a WAR, the J2EE standard states that the WEB-INF folder and its children cannot be access by URL request. So anything you put there can only be used by application logic and not served directly to clients.
When it comes to destroying a civilization, gas chambers cannot hold a candle to echo chambers.