[seam-issues] [JBoss JIRA] Updated: (SEAMFACES-79) Provide <s:restrictView> tag for securing pages

[Brian Leathem (JIRA)]

     [ https://issues.jboss.org/browse/SEAMFACES-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated SEAMFACES-79:
-----------------------------------

    Fix Version/s: 3.Future


> Provide <s:restrictView> tag for securing pages
> -----------------------------------------------
>
>                 Key: SEAMFACES-79
>                 URL: https://issues.jboss.org/browse/SEAMFACES-79
>             Project: Seam Faces
>          Issue Type: Feature Request
>          Components: UI Components, View Configuration
>    Affects Versions: 3.0.0.Beta2
>            Reporter: Dan Allen
>             Fix For: 3.Future
>
>
> Seam 2 had the ability to restrict pages using an EL expression or a permission from security. We have various ways we can provide this functionality in Seam 3. We should at least provide a view metadata tag [1] that coincides with <s:viewAction> to restrict a view.
> <s:restrictView require="#{identity.loggedIn}"/>
> <s:restrictView require="modify"/>
> It's import to ensure that Seam Security remains an optional dependency, just as with the managed-transaction feature.
> This feature was present in an early prototype of Seam 3, but got dropped. The source is still available for reference.
> https://fisheye.jboss.org/browse/~raw,r=11746/Seam/modules/faces/trunk/src/main/java/org/jboss/seam/faces/component/UIRestrictView.java
> https://fisheye.jboss.org/browse/~raw,r=11746/Seam/modules/faces/trunk/src/main/java/org/jboss/seam/faces/lifecycle/FacesSystemEventProcessor.java
> https://fisheye.jboss.org/browse/~raw,r=11746/Seam/modules/faces/trunk/src/main/java/org/jboss/seam/faces/lifecycle/AbstractViewMetadataProcesssor.java
> https://fisheye.jboss.org/browse/~raw,r=11746/Seam/modules/faces/trunk/src/main/java/org/jboss/seam/faces/lifecycle/EnforceViewRestrictionsProcessor.java
> [1] http://java.dzone.com/articles/bookmarkability-jsf-2

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira