(Related to Tynamo's tapestry-security, http://tynamo.org/tapestry-security+guide)
A custom exception handler added as an advice for the default one wants to handle some specific type of exceptions and proceeds to call PageResponseRenderer.render() in those cases. This works without issues in T5.1 but in T5.2 ComponentSource.getActivePage() throws "org.apache.tapestry5.ioc.internal.util.TapestryException: The identity of the active page for this request has not yet been established". To fix the issue, I can call the newly added RequestGlobabls.storeActivePageName(String pageName) before call to render(). While it's an easy fix, it'd be nicer if PageResponseRenderer.render() would just do that internally. Is there some reason why this would be a bad idea? Kalle --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
