[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Freedman resolved PORTLETBRIDGE-180.
--------------------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0-alpha
Code now parses the list (vs assuming only one) and tries each to see if the
resource exists when converting from .jsf (etc) to the actual valid suffix.
> Portlet Bridge 3.0.0 -- Update extension to view mapping to account for JSF
> 2.0 support of a list of mappable extensions
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: PORTLETBRIDGE-180
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-180
> Project: MyFaces Portlet Bridge
> Issue Type: Bug
> Components: Impl
> Affects Versions: 3.0.0-alpha
> Reporter: Michael Freedman
> Assignee: Michael Freedman
> Fix For: 3.0.0-alpha
>
>
> In JSF 2.0 an application can define multiple suffixes that are recognized as
> being processed by Faces (whereas in 1.2 you only had one). This means
> translating a viewId to an url requires walking this list and seeing if the
> underlying resource exists -- Also need vice-versa support.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
