Hi Rodrigue, > > As I said, I am now using a custom version of the identified > mechanism. However I am getting confused once again. When you say > "for that to work, you have to make sure that your authentication > element executes before the rest" > it seems to me that because all my elements inherit from the > authentication element, the authentication always executes before the > rest, does it not...?
You're correct. The last applications I developed with RIFE did not use inheritance for authentication, but rather an embedded element as a login box which then stored the credentials in the request as attributes, leaving the site accessible but to guests and authorized people. > By inheriting from Auth, am I not insured that > getRequestAttribute(Identified.IDENTITY_ATTRIBUTE_NAME) will return a > non-null value? Yes, you are. > Also, the existing documentation is already quite substantial, so > thanks to the work you and others have done. I'd be happy to try to > extend it as soon as I have time, which means once my project in which > I use rife is finished. Cool, every bit of help is much appreciated. Take care, geert -- Geert Bevin Terracotta - http://www.terracotta.org Uwyn "Use what you need" - http://uwyn.com RIFE Java application framework - http://rifers.org Music and words - http://gbevin.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "rife-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rife-users?hl=en -~----------~----~----~----~------~----~------~--~---
