-
1. Re: #{s:hasRole} causes authenticate method to re-run
gothmog Aug 27, 2007 5:05 AM (in response to gothmog)Further to this, it only happens if the #{identity.hasRole('abc')} EL is in a rendered attribute. You can have it in the page and the authenticate method doesn't get called.
Weird. Now I'm thinking it is really a bug
Troy -
2. Re: #{s:hasRole} causes authenticate method to re-run
gothmog Aug 27, 2007 5:26 AM (in response to gothmog)on playing around I would say this is happening:
1. Page A had a include to a menu.xhtml which uses the #{s:hasRole('abc') and if you look at the source for this it tries to log you in
2. On JSF page processing it must be processing this when in the rendered attribute and then again when the action command is executed.
Hence you get two calls on the authenticate in the same page processing cycle however one of them has the password set and the second call doesn't as it gets reset in the postAuthenticate call on the Identity class from the first pass through.
Make sure you don't have a EL reference to hasRole during your login sequence, it really confuses things!
A trap for young players
Cheers
Troy -
3. Re: #{s:hasRole} causes authenticate method to re-run
shane.bryzak Aug 27, 2007 9:28 PM (in response to gothmog)Which version of Seam are you using? I'm pretty sure this has been fixed in the latest CVS version.
-
4. Re: #{s:hasRole} causes authenticate method to re-run
gothmog Oct 14, 2007 5:59 PM (in response to gothmog)hi Shane,
I am using Seam 2.0.0.BETA1