You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Leonardo Uribe (JIRA)" <de...@myfaces.apache.org> on 2017/03/15 23:59:41 UTC

[jira] [Commented] (MYFACES-4103) Implement ViewHandler.getViews(...)

    [ https://issues.apache.org/jira/browse/MYFACES-4103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927219#comment-15927219 ] 

Leonardo Uribe commented on MYFACES-4103:
-----------------------------------------

I have committed a solution for this one, it was a long patch, but there are still some things to be solved. 

Specifically there is a mention in the javadoc of getViews(...) that says "... The elements in the stream are logical view ids. ..." . But right now in facelets there is no way to identify "template" files from "view" files. The case is problematic with resource library contracts, where composite components, views and template live together in the same path.

There is no mechanism defined in the spec for that, so we need something custom, problably as a faces-config-extension, and a way to detect composite components. 

This is important because if you want to use getViews(...) to create an automatically filled menu and a more modular JSF application, we need this feature to allow exclusions using patterns.

> Implement ViewHandler.getViews(...)
> -----------------------------------
>
>                 Key: MYFACES-4103
>                 URL: https://issues.apache.org/jira/browse/MYFACES-4103
>             Project: MyFaces Core
>          Issue Type: New Feature
>          Components: JSR-372
>            Reporter: Leonardo Uribe
>            Assignee: Leonardo Uribe
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)