In Tapestry 5, however, the whole framework looks to
a servlet container as one complicated filter that intercepts all the requests and does
with them whatever it thinks to be appropriate.
In the previous example, you can also see how certain values??”in this case the
package name of the application??”can be provided in the deployment descriptor to
be stored in application context??”a special piece of memory where these values can
be read later by the application.
This was a very brief overview of what a deployment descriptor is and what sort of
information it can contain. If you are curious to know more, or if you need to know
more to achieve the goals you are aiming for, please consult the Servlet Specification.
It is perfectly readable, unlike some other specifications, and very useful.
WAR Files Basics
The same Servlet Specification defines a very convenient way to package Java web
applications??”a Web Archive (WAR) file. This is basically the same as a JAR file,
which is an archived collection of files, The difference is that the WAR file contains
the whole web application's structure.
A WAR file can be distributed conveniently, and when it comes to deployment,
this file can be simply uploaded to a servlet container, and the latter will either
automatically unpack the contained web application or run it straight from the
WAR file.
Pages:
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305