[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-885) Restricting pages in pages.xml with wildcards

Gavin King (JIRA) jira-events at lists.jboss.org
Wed Mar 21 09:48:49 EDT 2007


     [ http://jira.jboss.com/jira/browse/JBSEAM-885?page=all ]

Gavin King closed JBSEAM-885.
-----------------------------

    Resolution: Rejected

I'm quite happy with how this works today.

> Restricting pages in pages.xml with wildcards
> ---------------------------------------------
>
>                 Key: JBSEAM-885
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-885
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: Security
>    Affects Versions: 1.1.6.GA
>         Environment: JBoss AS 5.0.0.Beta1
>            Reporter: Joshua Jackson
>         Assigned To: Shane Bryzak
>            Priority: Optional
>
> If I have directory structure for pages as such:
> /department/home.xhtml 
> /distributor/home.xhtml 
> I'll be able to secure it in pages.xml with wildcards as such:
> <page view-id="/**/*"> 
>    <restrict />
> </page>
> If I have directory structure as such:
> /order/purchase/home.xhtml 
> /order/sales/home.xhtml 
> I'll be able to secure it in pages.xml with wildcards as such:
> <page view-id="/order/purchase/*"> 
>    <restrict />
> </page>
> Since with this pattern it only works if we define the role in <restrict> element as such:
> <page view-id="/order/purchase/*"> 
>    <restrict>#{s:hasRole('admin')}</restrict>
> </page>
> Also this pattern:
> <page view-id="/order/**/*"> 
>    <restrict />
> </page>
> And this pattern:
> <page view-id="/**/**/*"> 
>    <restrict />
> </page>

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the seam-issues mailing list