Java Reference
In-Depth Information
• Routes requests through action beans, involving the full Stripes
request-response life cycle and giving us more control over what
happens between the stages of this life cycle
• Restricts the URLs used to access the application, making it easier
to control security
• Targets action beans instead of JSPs, making our code refer to
class names instead of URLs
2.4
Wrapping Up
You now have a working development environment and a Stripes appli-
cation up and running. I hope you've gained a better understanding of
the basics of Stripes by looking at the action bean and JSP code.
Here are a few things to notice after completing this exercise:
• Setting up a Stripes application does not stray from the standard
procedure for a Java web application, and Stripes has very few
dependencies.
• Stripes requires very little configuration. You just need to set up
the Stripes modules in the standard
web.xml
file and indicate the
root(s) of the packages that contain your action beans.
• You can add, remove, and rename action beans without having to
make changes to the configuration. Stripes will automatically find
and load your action beans, as long as they are in a package or
subpackage of the roots you've configured.
• Day-to-day work involves action beans and JSPs, not configura-
tion files.
• Your JSPs can link to action beans by class name, making the
association crystal clear and shielding your code from the details
of URL binding.
• The
${actionBean}
expression allows you to generically refer to the
current action bean and to its properties.
• You can trigger event handlers on action beans by writing a meth-
od that has the appropriate signature and referring to the name of
the method in the JSP.
In the next chapter, we'll discover more about action beans, JSPs, and
how they work together. We'll learn how to create HTML forms with
Stripes. We'll also start the main sample application that we'll be work-
ing on for the remainder of the topic.
Search WWH ::
Custom Search