I'm using a custom authentication for a public site, and I had a simple idea: why do I have to declare explicitly which urls should be secured? I can let the paragraphs (or templates) that need an authenticated user throw an exception if the user is not logged in, catch it in a Magnolia filter and redirect the user to the login page. This way all and only pages that contain "secured" paragraphs are secured, without bothering to put them all under the same path. Seemed easier for me and for the editor (paying the price of redirecting after half-rendering the page, but seemed acceptable). But the cms:include jsp tag won't allow me to do that. Include class just catches and stop any exception thrown, included runtime exceptions. Even when using a custom paragraph renderer (stripes in my case), if templates are jsps there seems to be no way of having an exception passing though. I suppose that it's impossible to change this behaviour because of jsp tag interface. Or am I missing some point? Am I doing something meaningless trying this road? Is there a standard exception handler in Magnolia that I missed? Anybody already tried anything similar?
Thanks for any advice.
Regards, Danilo. ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
