After updating from 5.0.9 to 5.0.10 the acegi component didn´t work, no login is possible because the login page is not shown. Instead it shows an error in the @BeginRender Queue. We localized the problem in the AcegiExceptionTranslationFilter class (internal service of tapestry acegi) in the function doFilter:
... catch (TapestryException ex) { if (ex.getCause() instanceof AuthenticationException || ex.getCause() instanceof AccessDeniedException) { handleException(request, response, chain, (AcegiSecurityException) ex.getCause()); } else { throw ex; } } ... 5.0.10 seems to encapsulate the TapestryException twice, so acegi throws an unkown TapestryException here. Our Workaround looks like this: ... catch (TapestryException ex) { if (ex.getCause().getCause() instanceof AuthenticationException || ex.getCause().getCause() instanceof AccessDeniedException) { handleException(request, response, chain, (AcegiSecurityException) ex.getCause().getCause()); } else { throw ex; } } ... But this is just for keep on developing and not standing still. Will there be an update for tapestry-acegi soon ? Best Regards Andreas -- View this message in context: http://www.nabble.com/T5-5.0.10-Acegi-doesn%C2%B4t-work-tp15454642p15454642.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]