XSLT and EJB
Now that the options for web tier development have been examined, let’s look at how the web tier interacts with other tiers in large enterprise class systems. A typical EJB architecture involves a thin browser client, a servlet-driven web tier, and EJB on an application server tier. Figure 4-7 expands upon the conceptual XSLT model presented earlier.

Figure 4-7. XSLT and EJB architecture
This diagram is much closer to the true physical model of a multitier
web application that uses XSLT. The arrows indicate the overall flow
of a single request, originating with the client. This client is
typically a web browser, but it could be a cell phone or some other
device. The client request goes to a single servlet and is handed off
to something called
RequestHandler
.
In the pattern outlined here, you create numerous subclasses of
RequestHandler. Each subclass is responsible for
validation and presentation logic for a small set of related
functions. One manageable strategy is to design one subclass of
RequestHandler for each web page in the
application. Another approach is to create fine-grained request
handlers that handle one specific task, which can be beneficial if
the same piece of functionality is invoked from many different
screens in your application.
The request handler interacts with the application server via EJB components. The normal pattern is to execute commands ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access