[ https://jira.jboss.org/jira/browse/JBSEAM-3749?page=com.atlassian.jira.pl... ] Przemyslaw Jaskierski updated JBSEAM-3749: ------------------------------------------ Description: There is a lot of scenarios which are impossible to accomplish without EL support in login-required attribute. Example: some pages should be freely accessed by recognized users (users who have e.g. you cookie set in it), but require login or registration from unrecognized users. Conditional check against e.g. session-scoped bean in login-required would be clean an elegant way to achieve this. Ok, you can add several intermediate views and redirect amongst them to achieve this, but it looks ridiculous comparing to clean EL approach. (was: There is a lot of scenarios which are impossible to accomplish without EL support in login-required attribute. Example: some pages should be freely accessed by recognized users (users who have e.g. you cookie set in it), but require login or registration from unrecognized users. Conditional check against e.g. session-scoped bean in login-required would be clean an elegant way to achieve this.) -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-3749?page=com.atlassian.jira.pl... ] Shane Bryzak commented on JBSEAM-3749: -------------------------------------- Can't you just use the <restrict> tag to achieve the same result? -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-3749?page=com.atlassian.jira.pl... ] Shane Bryzak commented on JBSEAM-3749: -------------------------------------- If the user isn't logged in then a NotLoggedInException will be thrown, not an AuthorizationException. And if you have pages.xml correctly configured, you will be redirected to the login page, not an error page. -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-3749?page=com.atlassian.jira.pl... ] Shane Bryzak commented on JBSEAM-3749: -------------------------------------- If your user isn't logged in and your restriction expression (either condition, your expression contains an 'or') evaluates to false, a NotLoggedInException will be thrown. And yes, you'll be redirected to the login page after which if you authenticate successfully you'll then be redirected back to x.html. -- 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