Another option is to check for authorization in the action class corresponding to the raw screen. This is of course, assuming you have an action class for the raw screen.
Rajeev ----- Original Message ----- From: "Darren Gilroy" <[EMAIL PROTECTED]> To: "'Turbine Users List'" <[EMAIL PROTECTED]> Sent: Thursday, February 14, 2002 11:19 AM Subject: RE: RawScreen > Eric - > > Yes, actually. Basically, I want to create a RawSecureScreen, just like a > VelocitySecureScreen. If you look at VelocityScreen as analogous to > RawScreen, I think it follows that RawScreen.doBuild() basically equals > VelocityScreen.doBuildTemplate( RunData ), and RawScreen.doOutput() is > basically what VelocityScreen.doBuildTemplate( RunData, Context ) is. > > So, I figured to create an abstract RawSecureScreen, by overriding doBuild, > and putting the "if (isAuthorized)" call in there. Then I could create > "actual" screens that extend RawSecureScreen, and then they would > automatically call the isAuthorized method. Whew! > > Does that make sense? I worked around it by just making my RawSecureScreen > extend Screen directly, but... > > Thanks! > -best-darr- > > -----Original Message----- > From: Eric Dobbs [mailto:[EMAIL PROTECTED]] > Sent: Thursday, February 14, 2002 9:06 AM > To: Turbine Users List > Subject: Re: RawScreen > > > On Thursday, February 14, 2002, at 08:49 AM, Darren Gilroy wrote: > > > The doBuild() method in org.apache.turbine.modules.screens.RawScreen is > > declared final. > > I believe the intended use of RawScreen is to override the doOutput() > in your subclass -- which gets called by doBuild(). > > Is there some reason that doesn't work for you? > -Eric > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
