Ahh... I was digging about and found this nugget http://www.nabble.com/wicket-security%2C-everybodyprincipal-and-only-securepages-td15413102.html#a15419077 here
"......since you probably want every page to extend BasePage why not have a subclass that implements ISecurePage and have all your pages that should be secure extend that page. For the implementation of ISecurePage you can simply redirect all calls to the SecureComponentHelper." Looks like SecureComponentHelper is the answer to my problems. Thanks for your help. Neil McT wrote: > > > So, in terms of WASP / SWARM... what is it that makes SecureBasePage > secure? I.e. it doesn't extend SecureWebPage. I'm assuming, therefore, > that it implements ISecurePage? > > ...... > > -- View this message in context: http://www.nabble.com/Markup-inheritance-for-secure-and-non-secure-pages-tp18952852p18953560.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
