ChangeLog From Public Review version:
- Chapter 3: Bridge Interface
- section 3.2: adds specification for defaultRenderKitId attribute
- section 3.2 removes specification for bridgeWriteBehindResponseClassName attribute
- Chapter 4: GenericFacesPortlet
- section 4.1: Removed defaultContentType, defaultCharacterSetEncoding and bridgeWriteBehindResponseClassName portlet initialization parameter.
- section 4.1 Added defaultRenderKitId portlet initialization parameter.
- section 4.2: removed use of getWriteBehindResponse().
- section 4.2: indicated getResponseContentType() and getResponseCharacterSetEncoding() are now deprecated.
- section 4.2: added getDefaultRenderKitId() usage.
- section 4.2.1: init() no longer uses the (removed) getBridgeWritebehindResponse()
- section 4.2.1: init() calls getDefaultRenderKitId().
- section 4.2.10: getResponseContentType changed to indicate its deprecated.
- section 4.2.11: getResponseCharacterSetEncoding changed to indicate its deprecated..
- section 4.2.16: section added to descibe GenericFacesPortlet impl for getDefaultRenderKitId
- section 4.2.16: existing section (getWriteBehindResponse) removed.
- Chapter 5: Bridge Lifecycle Requirements
- section
5.1.2: clarified that during a resource request the scope isn't
restored into the current request but reserved for latter use/update.
- section
5.2.7: removed bullet indicating the need to ensure isPostback()
returns true in a resource request. This was mistakenly copied
from the render description.
- section 5.3: clarified that PRP are only updated by the bridge in an action or event request.
- section 5.3.3: clarified that PRP are only updated by the bridge in an action or event request.
-
Chapter 6: Bridge Requirements for Managing Faces
- section 6.1.3.1: dispatch(): clarified situations in which the bridge may use include instead of forward to dispatch
- section
6.1.3.1 encodeActionURL(): clarified that when DirectLink is used the
bridge is repsonsible for checking/returning an absolute URL.
- section
6.9: Added this section to describe how the bridge satisfies/ensures a
portlet that wants to use a distinct renderkit (from other portlets) can do so.
- Chapter 7: BridgeRenderFilter
- General
rewrite to clarify that there are now 2 mechanisms for use to implement
JSF jsp write behind response support: use a servlet filter or
wrap the portlet response.