Hi folks, I'm new to Wicket so please forgive me if I ask something incredibly dumb :)
I've just started using Wicket and am enjoying it very much. I'm putting together an application using SWARM / WASP for my authentication / authorisation and would like to use markup inheritance to give a consistent look and feel for both secure AND non-secure pages.. and this is where I've run into my first problem. I would like all off my pages to extend some base-page however my secure pages all extend SecureWebPage. So basically my secure and non-secure web pages cannot extend the same base page. As far as I can see my options are.... 1) Rather than extend SecureWebPage my secure pages can implement ISecurePage, however this would require quite a few additional methods to be implemented (and duplicated) across my secure pages. 2) Rather than go for a page-based layout I could go for a single page with a panel-based layout and manage security on a panel-by-panel basis. However, I prefer the navigation aspect of the page-based layout and I prefer to assign permissions in SWARM on a page-by-page basis (and find it easier / more intuitive to authenticate on a page-basis). Am I missing something simple here? Does anyone have any other suggestions? Any help much appreciated, Neil. -- View this message in context: http://www.nabble.com/Markup-inheritance-for-secure-and-non-secure-pages-tp18952852p18952852.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]
