On 9/9/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Rick Reumann <[EMAIL PROTECTED]> wrote on 09/09/2005 12:01:48 PM: > > > > > I would think JSF could use regular servlet filters? If so, that's where > > > I'd do stuff that you want checked on almost every request. Even in > > Struts, I wouldn't touch the RequestProcessor. Use a ServletFilter. > > oh yes, correct! I do remember writing those when I worked with Struts.. > This is in fact what I meant..:) > > They > > are easy to set up and I'll provide an example if you want one. I'm not > > sure of the implications of using them with JSF, but I'm sure they could > > > be used. > > Yes, those implications you mentioned are I guess what I'm wondering > about.. (thanks for articulating it for me..;))
A servlet filter is definitely usable with JSF (and therefore with Shale), and is an appropriate solution to this problem, just like it is for a Struts 1.x application. For Shale in particular, the "application controller" part of Shale is implemented as a Commons Chain chain (similar in spirit to what's going on with Struts 1.3's request processor), so you can also implement a check like this as one of the commands that gets executed on every request. To set up such commands, simply configure a chain named "preprocess" in catalog "shale" and it will get executed for you on every request. > > > -- > > Rick > > Geeta > > Craig
