Laurie Harper <[EMAIL PROTECTED]> writes:
>The screen modules (classes in .../modules/screens) in the generated app
>extend VelocitySecureScreen (I think it is), which is where the
>authentication requirement is implemented. If you define your screens to
>exten VelocityScreen instead of VelocitySecureScreen the requirement to
>log in wont be imposed.
>I think... :)
You're correct. You must also change the action.sessionvalidator
property to use the "sessionvalidator.TemplateSessionValidator" and not
the "sessionvalidator.TemplateSecureSessionValidator".
Else you will get sent to the screen defined in screen.login.
Regards
Henning
>L.
>�� �� wrote:
>> Hi all, I am using turbine 2.1. I don't want turbine to perform access
>> controlling to some pages of my web site. How should I do? Could anyone
>> tell me?
>> Thank you.
>>
>>
>>
>>
>>
>> _________________________________________________________________
>> �����������ѽ��н�������ʹ�� MSN Messenger: http://messenger.msn.com/cn
>>
>> --
>> To unsubscribe, e-mail:
>>
>> For additional commands, e-mail:
>>
>>
>--
>To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
>For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH [EMAIL PROTECTED]
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 [EMAIL PROTECTED]
D-91054 Buckenhof Fax.: 09131 / 50654-20
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
