[ 
https://issues.apache.org/jira/browse/TRINIDAD-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859476#action_12859476
 ] 

Max Starets commented on TRINIDAD-1794:
---------------------------------------

Are you guys suggesting that we map *.jspx to Facelets in Trinidad? We have 
jsp-specific tags in those files (like jsp:root), and Trinidad does not
provide Facelet handlers for those. These tags will appear in the rendered 
output as plain text, which will cause other problems. 
Until we convert all the samples to pure Facelets, I believe we should leave 
these jspx files mapped to the JSP engine.

If the jsf.js script cannot be made available with JSPs, then we should be 
using the legacy PPR implementation for them, and f:ajax would be considered 
unsupported

> 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.

Reply via email to