[
https://jira.jboss.org/jira/browse/JBSEAM-3749?page=com.atlassian.jira.pl...
]
Przemyslaw Jaskierski commented on JBSEAM-3749:
-----------------------------------------------
Yes, I have pages.xml properly configured.
So:
<page view-id="x.xhtml">
<restrict>#{identity.loggedIn or
mySessionScopedCookieVerifier.hasUserOurCookieSet}</restrict>
</page>
will throw NotLoggedInException if both conditions evaluate to false, and after logged in
on the login page that I will be redirected to, I will be redirected to x.xhtml again?
Honestly saying it's a little bit weird comparing to the approach with EL in
login-required, which looks more consistent semantically.
login-required should support EL
--------------------------------
Key: JBSEAM-3749
URL:
https://jira.jboss.org/jira/browse/JBSEAM-3749
Project: Seam
Issue Type: Feature Request
Reporter: Przemyslaw Jaskierski
Assignee: Shane Bryzak
Fix For: 2.1.1.CR2
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.
--
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