[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632420#action_12632420
]
Scott O'Bryan commented on PORTLETBRIDGE-47:
--------------------------------------------
This won't effect Trinidad or Commons. We made this assumption but we always
retrieve any context we use from the ExternalContext. In this case, Tomahawk
needs to be able to do this from a servlet environment. I wrote a note to the
EG about this issue and will hopefully have an answer soon. I think it's
reasonable to expect a context object here and, if we can't provide one, we
need the spec to clearly define that we will receive a config.
The R.I. will of course be updated accordingly, so I'm going to keep this bug
open for now until we get final word.
> BridgeImpl pass PortletConfig instance to FacesContextFactory instead
> PortletContext
> ------------------------------------------------------------------------------------
>
> Key: PORTLETBRIDGE-47
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-47
> Project: MyFaces Portlet Bridge
> Issue Type: Bug
> Affects Versions: 1.0.0-alpha-2
> Reporter: Leonardo Uribe
> Priority: Critical
>
> On myfaces portlet bridge (for jsf 1.2) do this
> (org.apache.myfaces.portlet.faces.bridge.BridgeImpl line 240):
> try
> {
> // Get the FacesContext instance for this request
> context =
> getFacesContextFactory().getFacesContext(mPortletConfig, request,
> response, getLifecycle());
> It should pass a javax.portlet.PortletContext instance instead, because this
> is the expected var here.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
