[
https://jira.jboss.org/jira/browse/JBSEAM-4159?page=com.atlassian.jira.pl...
]
Arshad Mahmood commented on JBSEAM-4159:
----------------------------------------
Oops, sorry also a second enhancement that would be useful is an attribute like
prune="true"/"false". The purpose of prune would be to stop any
further processing rules (a la the unix find command). Again, this is useful to stop other
rules in the pages.xml being acted on later in the file (as currently *ALL* rules that
match are acted on).
The view-id attribute in pages.xml can be a pattern to match against
multiple pages, it would be very useful to have a exclude-view-id attribute to exclude
certain pages from being acted on.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-4159
URL:
https://jira.jboss.org/jira/browse/JBSEAM-4159
Project: Seam
Issue Type: Feature Request
Reporter: Arshad Mahmood
I have an application which required login-in for all pages except for the main login
page itself. If I enter a generic <page view-id="/view/*.seam"
login-required="true" /> then this causes problem with the login view itself
(which is at /view/login.seam). It would be much easier if I could write a rule like
<page view-id="/view/*.seam" exclude-view-id="/view/login.seam"
login-required="true" />.
Although, very useful in this scenario this enhacement I think would be worthwhile in
other situations too.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira