
sorry for the jargon I threw at you.
Yes, the recommended way of making a website that can be accessed by large number of users is to host the static content in a http server, and host the dynamic content in a web container like
Tomcat. You can look at
This for an explanation. It's not very easy to do for a beginner. If this is like a college project, you might want to forget I said anything
Most people do put their static content inside the webapp, and that's fine for most webapps. Web servers for the most part do a decent job of serving static content that usually it's not a problem. Also, if the static content is used in the dynamic pages, you will have to make sure apache is configured in each developer and qa machine, which creates a big hassle. So, to make it simple, most projects start with hosting static content in the webapp, and move it out to the http server when the load becomes very high
I was just thinking that in your case since these static pages are not developed by developers, and they are out of the way of the dynamic content, it might be easier for you to not bundle it with the dynamic content