-
Type:
New Feature
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: facesbridge-api-5.0.0, facesbridge-spec-5.0.0
-
Component/s: FacesBridge API, FacesBridge Spec
-
Labels:None
The JSR 329 Specification defined several configuration options that can be placed in the faces-config.xml descriptor. For example, Section 5.1.2.1 titled "Excluding Attributes from the Bridge Request Scope" requires that the implementation detect the presence of the bridge:excluded-attributes element:
<faces-config> <application> <application-extension> <bridge:excluded-attributes> <bridge:excluded-attribute>org.apache.myfaces.trinidadinternal.*</bridge:excluded-attribute> </bridge:excluded-attributes> </application-extension> </application> </faces-config>
Over the years, the following bridge projects attempted to define a class named BridgeConfig in order to define bridge configuration options:
- com.liferay.faces.bridge.BridgeConfig
- org.apache.myfaces.portlet.faces.bridge.config.BridgeConfig
- org.jboss.portletbridge.bridge.config.BridgeConfig.java
This issue serves as a proposal for promoting the following Liferay Faces Bridge classes from com.liferay.faces.bridge to javax.portlet.faces:
In addition, the Spec will require that the factory delegation chain pattern be supported by bridge implementations, so that instances of javax.portlet.faces.BridgeConfig can be decorated with javax.portlet.faces.BridgeConfigWrapper.
Update 2016/07/21: The JavaDoc descriptions for methods that return a Map or a Set have been updated to require the return values to be immutable. For more info, see FACES-2828.
- is related to
-
FACES-2828 BridgeConfig should return immutable values
-
- Closed
-