Hello all,
I hope I have not double-posted this message. For some reason my first post
to the list (yesterday night) never showed up so I'm trying again.
I've been using Turbine (2.1) for a few days now and I'm excited about its
potential. I'm still trying to better understand the inner workings of
Turbine's session and user validation scheme.
In my TR I have the following definitions:
action.sessionvalidator=sessionvalidator.TemplateSessionValidator
...
services.VelocityService.default.screen=VelocityScreen
If I request a template file that has no corresponding Java class (i.e.,
there is a templates/app/screens/Test.vm but no
WEB-INF/classes/.../screens/Test.class), the Login.vm screen is immediately
returned because I have not yet logged in.
But if I simply create a Test.java class that extends the VelocityScreen
class like so:
package com.etc.turbine.screens;
import org.apache.velocity.context.Context;
import org.apache.turbine.util.RunData;
import org.apache.turbine.modules.screens.VelocityScreen;
public class AboutTechspace extends VelocityScreen {
}
And I then request the same template Test.vm file again, it is returned to
me even when I'm not logged in. Here's where I'm getting confused:
according to my TR, the default screen class should be VelocityScreen for
those templates called without a corresponding Java class, right? If so,
then how does the simple addition of the class above make Turbine ignore the
user logged in check? And where in the code should I be looking?
BTW, is this the best solution to keep a set of pages "public"? Right now I
have about 5-8 links from my homepage that I want to be available to anyone.
Once the user is logged in, then I want all other links to be restricted
(which is being done automatically by TemplateSessionValidator and
VelocitySecureScreen).
Thanks,
Daniel.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
