Finally, your web app is ready for prime time. Your pages are polished, your code is tested and tuned, and your deadline was two weeks ago. But where does everything go? So many directories, so many rules. What do you name your directories? What does the client think they’re named? What does the client actually request, and how does the Container know where to look? How do you make certain that you don’t accidentally leave out a directory when you move the whole web app to a different machine? What happens if the client requests a directory instead of a specific file? How do you configure the DD for error pages, welcome files, and MIME types? It’s not as bad as it sounds...
Web Application Deployment
Construct the file and directory structure of a web application that may contain (a) static content, (b) JSP pages, (c) servlet classes, (d) the deployment descriptor, (e) tag libraries, (f) JAR files, and (g) Java class files. Describe how to protect resource files from HTTP access.
Describe the purpose and semantics for each of the following deployment descriptor elements: error-page, init-param, mime-mapping, servlet, servlet-class, servlet-mapping, servlet-name, and welcome-file.
Construct the correct structure for each of the following deployment descriptor elements: error-page, init-param, mime-mapping, servlet, ...