[
https://issues.apache.org/jira/browse/MYFACES-2380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe resolved MYFACES-2380.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.2.8-SNAPSHOT
> DefaultRestoreViewSupport.calculateViewId does not calculate viewId properly
> on portlet case
> --------------------------------------------------------------------------------------------
>
> Key: MYFACES-2380
> URL: https://issues.apache.org/jira/browse/MYFACES-2380
> Project: MyFaces Core
> Issue Type: Bug
> Components: Portlet_Support
> Affects Versions: 1.2.7
> Environment: liferay 5.2.3, myfaces portlet bridge 1.0.0-beta-2,
> myfaces core 1.2.7
> Reporter: Leonardo Uribe
> Assignee: Leonardo Uribe
> Fix For: 1.2.8-SNAPSHOT
>
>
> Testing the helloworld portlet archetype on liferay for many, many hours, I
> have seen a problem with the way it is resolved the view id
> In this configuration, the current algorithm resolves the view id using
> javax.servlet.include.path_info
> and
> javax.servlet.include.servlet_path
> But in portlet case, this values should not be taken into account. Instead,
> we have to check if this is a portlet request or not (it seems
> javax.portlet.faces.PORTLET_LIFECYCLE_PHASE is used to check if is a portlet
> request or not) and call:
> org.apache.myfaces.portlet.faces.context.PortletExternalContextImpl.getRequestPathInfo()
> or getRequestContextPath() when necessary.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
