[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029877#comment-13029877
]
Neil Griffin commented on PORTLETBRIDGE-192:
--------------------------------------------
Regarding #1, #2, and #4: Sounds fine, I could go either way.
Regarding #3: I've implemented BridgeContext and BridgeConfig and found that
the getPortletConfig() and getDefaultViewIdMap() belong on BridgeContext. This
is because BridgeContext contains information about the "current" portlet-name
from portlet.xml, since more than one portlet can be defined in portlet.xml.
When I had those methods on BridgeConfig, I found that
BridgeConfig.getPortletConfig() didn't know which portlet-name to work with,
since it is didn't know what the "current" portlet was. For example, getting
context-param values.
> 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
