such a check belongs in ISecurityStrategy and not really in your page hierarchy. see wicket-auth-roles for examples.
-igor On Tue, Apr 1, 2008 at 10:28 AM, Bruce Petro <[EMAIL PROTECTED]> wrote: > I'm just getting started in wicket, so forgive me if this is a too-dumb > question... > > > > I know wicket can check the session for a user to ask a "user" object if > it is logged in. > > However, you don't really want to paste code on every page. > > What is the best way, to have each page inherit the base "security > check" routine? > > > > Would you create a BasePage extends WebPage and put the logic there and > have all other pages extend BasePage? > > Or would you attach some sort of a command object to each page and put > the logic in that? > > > > Anyone have a reference to an example of code to do this? > > > > THANKS! > > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
