You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Martin Goldhahn (JIRA)" <de...@myfaces.apache.org> on 2007/12/27 09:43:43 UTC

[jira] Updated: (MYFACES-1792) Interface org.apache.myfaces.portlet.DefaultViewSelector should see the portletConfig

     [ https://issues.apache.org/jira/browse/MYFACES-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Goldhahn updated MYFACES-1792:
-------------------------------------

    Status: Patch Available  (was: Open)

> Interface org.apache.myfaces.portlet.DefaultViewSelector should see the portletConfig
> -------------------------------------------------------------------------------------
>
>                 Key: MYFACES-1792
>                 URL: https://issues.apache.org/jira/browse/MYFACES-1792
>             Project: MyFaces Core
>          Issue Type: Improvement
>    Affects Versions: 1.1.5
>         Environment: JDK 1.5, Liferay 4.3.5
>            Reporter: Martin Goldhahn
>            Priority: Trivial
>
> The problem with the current impementation is that you have to put the information for which view to use in the portlet context (equiv. servlet context). This is sufficient where you ship just one portlet per war, i.e. servlet context. It doesn't work when you put two portlets inside the same servelt context (to get communicatino between portlets working).
> It would be much better to make the DefaultViewSelector see the portlet config by adding a function public void setPortletConfig(javax.portlet.PortletConfig cfg) to the interface. 
> The PortletContet is accessable from the PortletConfig, thus the setPortletContext function can be deprecated.
> A temporary solution to the problem is to override MyFacesGenericPortlet.init() and set the portletConfig after super.init().

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.