[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029606#comment-13029606
]
Alexandr Smirnov commented on PORTLETBRIDGE-192:
------------------------------------------------
There are my opinion:
1) To keep BridgeContext smaller, do not put information that available by
other API there: Context, Request and Response objects etc.
2) Make BridgeContext as an abstract class with ThreadLocal instance variable,
similar to the FacesContext. BridgeContext should be created before
FacesContext and released after that.
3) put default view id's belong to the BridgeConfig
> Proposal for 3.0 API: javax.portlet.faces.context.BridgeContext and
> associated BridgeContextFactory
> ---------------------------------------------------------------------------------------------------
>
> Key: PORTLETBRIDGE-192
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-192
> Project: MyFaces Portlet Bridge
> Issue Type: New Feature
> Components: General
> Affects Versions: 3.0.0
> Reporter: Neil Griffin
> Assignee: Michael Freedman
>
> This class contains contextual information related to the bridge. It is
> inherently request scoped, and is useful for sharing data between
> implementations of Bridge.java and ExternalContext.java
> Please refer to the following classes for this proposal:
> http://svn.portletfaces.org/svn/portletfaces/bridge/portletfaces-bridge-api/trunk/src/main/java/org/portletfaces/bridge/context/BridgeContext.java
> http://svn.portletfaces.org/svn/portletfaces/bridge/portletfaces-bridge-api/trunk/src/main/java/org/portletfaces/bridge/context/BridgeContextFactory.java
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
