Here is the outline of such a structure:
Perhaps the most important part of it is the WEB-INF directory. It is the brain
and heart of a Java web application. The contents of this directory are protected
by the servlet container??”it prevents anyone from navigating to, say, http://www.
someserver.com/myapp/WEB-INF/ and seeing what this directory contains.
The WEB-INF/classes subdirectory is where the compiled Java classes go??”those
classes that we create for our application, such as page classes.
The WEB-INF/lib subdirectory is for the libraries used by the application, such as the
Tapestry framework libraries. Any class or resource stored here should normally be
packaged in a JAR file.
Appendix A
[ 247 ]
The web.xml file which must be present inside the WEB-INF directory is a
deployment descriptor??”it is described in the next section. Also, the WEB-INF
directory can contain other files as needed by the application.
There can be another hidden directory in a Java web application, META-INF. It can
contain other useful information about the application.
All the other files and directories, those outside WEB-INF and META-INF , are
accessible from the Web. This means that if we have have a JSP page named
somePage.
Pages:
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301