Answering to first question:
I don't know if it is better way, but try to inherit your
screens from different Turbine classes.
For "public" screens simply extend VelocityScreen
but if you want to secure things - extend VelocitySecureScreen.
For example:
class SendEnquiry extends VelocityScreen - this is a public page
Create "backbone " for secured pages:
public abstract class AdminScreen extends VelocitySecureScreen
{
protected boolean isAuthorized(RunData data)
{
// perform authorization checks
}
}
Now for protected page:
class ProtPage extends AdminScreen
Hope this helps
Oskar
>
> However, to make things at least a bit on topic for this list,
> I'll also ask about using TemplateSecureSessionValidator
> I've deployed a web application running at
>
> http://www.softghana.com:8080/servlet/takashie/
>
> and currently, anyone can use the backend. I'd like to use
> TemplateSecureSessionValidator but there are a couple of
> screens like
>
> http://www.softghana.com:8080/servlet/takashie/template/SendEnquiry.vm?inte
>rest=bimbilla
>
> that should allow public anonymous access. I tried writing my own
> MyTemplateSecureSessionValidator that munges the code for
> TemplateSecureSessionValidator to make an exception for the public
> anonymous accessible screens.
>
> Is there a better way to mix screens that require login and screens
> that do not require login ?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
