well, upon further reading i found in the docs the phrase:
. If you would like to allow the user to view multiple pages without the
need to login first, you will need to implement your own version of
SessionValidator that just returns nothing as a result.
does anyone have a simple example of this?
aash
aash wrote:
> I was able to get an app to login and move around properly,
> and default back to login when you tried to access a link without
> logging in, or when your password was illegal etc.
>
> (by commenting out screen.login and screen.homepage in TR.props.
> i added a template.login to TR.props. i changed action.sessionvalidator
>
> to sessionvalidator.TemplateSecureSessionValidator (from
> TemplateSessionValidator)
>
> what i was wonder is how to make a few pages available without logging
> in first, i.e. changing the sessionvalidator on the fly. (for a
> Register, Forgot
> Password, or Help page, for instance)
>
> the code in Turbine.java says:
>
> // This is where the validation of the Session information
> // is performed if the user has not logged in yet, then
> // the screen is set to be Login. This also handles the
> // case of not having a screen defined by also setting the
> // screen to Login. If you want people to go to another
> // screen other than Login, you need to change that within
> // TurbineResources.properties...screen.homepage; or, you
> // can specify your own SessionValidator action.
> ActionLoader.getInstance()
> .exec( data,
> TurbineResources
> .getString("action.sessionvalidator") );
>
> i assume since it's getting this straight from TR that you can't really
> override it
> on the fly, but you have to make a new session validator that handles
> the
> "dual" mode? what is the standard way to handle this?
>
> aash
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
