Hello, I have been playing around with authorization strategies and I have noticed that even though components that are not authorized to RENDER, its header contributions are still going through. I understand that isVisible != RENDER as discussed in previous threads however I feel there is a practical need to be able to prevent header contributions from going through if a component is not rendered.
My case in point is that I have certain heavy components that should not be rendered to users not logged in and I would prefer that all the excess javascript, css and other header contributions are not displayed. As a temporary work around and I am overriding isVisible in these heavy components and doing the necessary authorization checks there. Although it works, it isn't very elegant as my authorization strategy is now decoupled across the whole application. Any thoughts on this are appreciated! Regards. -- View this message in context: http://www.nabble.com/Header-contributions-despite-failed-RENDER-authorization-tp19235888p19235888.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]
