RE: Question on page inheritance...

e { >httpSession.setAttribute("sso.password.attribute", null); >httpSession.setAttribute("sso.email.attribute", null); >} >} > >public Person getPerson() { >if (person != null) { >return person

Question on page inheritance...

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 "s