Re: TemplateSecureSessionValidator

2000-12-20 Thread James Coltman
in TR.props? I even created another sessionvalidator and copied the code from TemplateSecureSessionValidator and put in debugging prints. Interestingly enough, data.getTemplateInfo().setScreenTemplate( TurbineResources.getString("template.login") ); System.out.println(data.getTe

RE: TemplateSecureSessionValidator

2000-12-20 Thread James Coltman
Subject: Re: TemplateSecureSessionValidator Unfortunately, none of the code since TDK1.1a9 works with the TDK anymore because of significant changes in the security model - all the OM classes and DB schema have changed since the last TDK. So right now, no, there's not a way to (easily) replace

Re: TemplateSecureSessionValidator

2000-12-02 Thread Martin Poeschl
Will Stranathan wrote: Which version of Turbine are you using? With TDK1.1a9 and TDK1.1b1, I get the same results. Is there something else I'm missing in TR.props? I even created another sessionvalidator and copied the code from TemplateSecureSessionValidator and put in debugging prints

TemplateSecureSessionValidator

2000-12-01 Thread Will Stranathan
Does the TemplateSecureSessionValidator work with Velocity? If I set action.sessionvalidator=sessionvalidator.TemplateSecureSessionValidator in TR.props, does that mean that if I try to go directly to /template/foo.vm, I should get redirected to template.login, right? For some reason

Re: TemplateSecureSessionValidator

2000-12-01 Thread John McNally
It should work the same as for WebMacro. I would call it a bug if it is isn't. But I don't know right off hand what the difference could be. Will Stranathan wrote: Does the TemplateSecureSessionValidator work with Velocity? If I set action.sessionvalidator

Re: TemplateSecureSessionValidator

2000-12-01 Thread Will Stranathan
work the same as for WebMacro. I would call it a bug if it is isn't. But I don't know right off hand what the difference could be. Will Stranathan wrote: Does the TemplateSecureSessionValidator work with Velocity? If I set action.sessionvalidator

Re: TemplateSecureSessionValidator

2000-12-01 Thread Dave Bryson
On Fri, 01 Dec 2000, you wrote: Does doPerform() get called from it automatically by Turbine? Or do I need to call it from the module? From what I can tell, doPerform() just isn't ever getting called on it for some reason. Yes. The sessionvalidator is an action so it's called

Re: TemplateSecureSessionValidator

2000-12-01 Thread Will Stranathan
Yup. And if I just go to appname/servlet/appname, it goes to the login screen if I'm not logged in. But if I'm not logged in, I can still explicitly set the template. Will On Fri, 1 Dec 2000 21:42:44 -0600 Dave Bryson [EMAIL PROTECTED] wrote: On Fri, 01 Dec 2000, you wrote: Does

Re: TemplateSecureSessionValidator

2000-12-01 Thread Dave Bryson
template and I set the TemplateSecureSessionValidator. Without being logged in I'm redirected to the login even if I explicity point to another template. -- Dave Bryson [EMAIL PROTECTED] -- To subscribe

Re: TemplateSecureSessionValidator

2000-12-01 Thread Will Stranathan
Which version of Turbine are you using? With TDK1.1a9 and TDK1.1b1, I get the same results. Is there something else I'm missing in TR.props? I even created another sessionvalidator and copied the code from TemplateSecureSessionValidator and put in debugging prints. Interestingly enough