Chapter 2:
this
chapter provides a short overview of portlets, JSF, and the bridge
architecture. It also introduces you to the terminology used
in the specification.
Chapter 4:
this chapter defines the behavior of the
GenericFacesPortlet; a bridge provided portlet implementation that you
will commonly subclass to build your portlet. It hides all
the details of initializing, configuring, managing, and
executing the bridge.
Chapter 3:
this chapter defines the bridge interface and configuration
which a portlet uses to initialize, configure, manage, and execute it.
I.e. defines the interface and configuration details hidden
to you in chapter 4 by the GenericFacesPortlet implementation.
Chapter
6, section 6.5 through subsection 6.5.2.1 plus section
6.5.2.3:
these sections provide information related to portlet
specific EL evaluation.
Chapter
6, section 6.8:
JSF provides a facility allowing managedbean implementors to be
notified before the bean is destroyed. This section includes
important information for supporting this notification (correctly) in a
portlet environment.
Chapter
5, section 5.1:
this section describes how the portlet and JSF lifecycles
differ
and how the bridge manages state to ensure expected behavior in JSF.
You will need to understand this information and how to
exclude
specific state from being managed by the bridge if you determine that
such state management is detrimental/not needed.
Chapter 7:
this chapter defines the behavior of a servlet filter that
can be
used with the bridge to provide correct markup ordering when your JSF
view is represented by a jsp whose output comes from regular jsp markup
as well has JSF components. Note: filter
implementations
aren't part of the formal specification because JSF is structured in
such a way as to require distinct implementations per JSF
implementation. If you need such a filter to correct the jsp
ordering problem you will have to search for a publicly available
implementation for your JSF implementation type or write one yourself.