jsp, it can be seen by anyone by navigating to something like
http://www.someserver.com/myapp/somePage.jsp. Typically you will find here
HTML and JSP pages as well as images and stylesheets. Naturally, they all can be
put into as many different directories as is convenient.
Returning to the web.xml file, we never had any need to look into it in the course
of the book, so it is actually not necessary to know its contents. But sometimes such
knowledge can be useful, so let's have a look into deployment descriptor.
The Basics of the Deployment Descriptor
The Deployment descriptor, which is a web.xml file, serves to tell a servlet container
important details about a Java web application. Most commonly, it defines the
servlets of the application and associates them with certain URL patterns, so that the
servlet container knows which request should be passed to which servlet. Here is
an example of a deployment descriptor, the one that would be typically be used in a
Tapestry 4 application:
xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.
Pages:
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302