[
https://issues.apache.org/jira/browse/TRINIDAD-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859485#action_12859485
]
Werner Punz commented on TRINIDAD-1794:
---------------------------------------
Actually maybe I was a little bit unprecise here, as I wrote down before, we in
our behavior regarding JSPX are faulty but I was not sure if the setting itself
was intentionally left out in the demo or not since it was set up until
recently in the branch, as it seems it was intentional.
> Possible settings bug in the web.xml of the 2.x Trinidad demos
> --------------------------------------------------------------
>
> Key: TRINIDAD-1794
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1794
> Project: MyFaces Trinidad
> Issue Type: Bug
> Affects Versions: 2.0.0-alpha-2
> Reporter: Werner Punz
>
> While investigating the Trinidad ppr demos I found following bugs:
> The Facelets View Mappins were set only to xhtml which then caused
> that jsf.js could not be included since it relies on having a valid head
> element
> that MyFaces failed due to a MyFaces 2 bug in conjunction of ppr + jspx
> (which will be further investigated)
> changing
> <context-param>
> <param-name>javax.faces.FACELETS_VIEW_MAPPINGS</param-name>
> <param-value>*.xhtml</param-value>
> </context-param>
> to
> <context-param>
> <param-name>javax.faces.FACELETS_VIEW_MAPPINGS</param-name>
> <param-value>*.xhtml;*.jspx</param-value>
> </context-param>
> Resolved both issues, I am not sure if the setting was intentional, on the
> 2.x preparation branch the setting was on, but along the way it got lost.
> I am adding this bug for documentation purposes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
