This way it frees servlet developers to write code
specific only to their application.
However, writing Java code at the level of servlets is still rather low-level work, and
many Java web frameworks appeared to provide ready-to-use solutions for common,
repeating tasks. Frameworks are ultimately based on the Servlet API, but building
web applications with them is much easier, and more efficient, than working on the
level of servlets.
Tapestry 5 is perhaps the most advanced and the most developer-friendly of the Java
web frameworks, and so it shields us very efficiently from the nitty-gritty of servlet
specification. However, there are a few pieces of servlet-related information that will
be useful for us, such as:
1. The standard structure of a Java web application.
2. The basics of a deployment descriptor.
3. The basics of a WAR file.
The Basics of Java for the Web
[ 246 ]
It might also be useful to mention different kinds of Java-enabled servers so that you
can decide which one of them to use.
The Standard Structure of a Java Web
Application
A Servlet container requires every Java web application to have a certain structure so
that it can manage the application properly.
Pages:
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300