Thanks I will look into that. chris
Howard M. Lewis Ship (JIRA) wrote:
[ https://issues.apache.org/jira/browse/TAPESTRY-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Howard M. Lewis Ship closed TAPESTRY-2025. ------------------------------------------ Resolution: Won't Fix Assignee: Howard M. Lewis Ship I think the correct way to address your access control scenario is by plugging into the ComponentEventRequestHandler and PageRenderRequestHandler pipelines. These pipelines support filters and are invoked only once the details of the request (i.e., page name, component, contexts, etc.) is established.Centralize page/component class resolution logic ------------------------------------------------ Key: TAPESTRY-2025 URL: https://issues.apache.org/jira/browse/TAPESTRY-2025 Project: Tapestry Issue Type: Improvement Components: Framework, tapestry-core Affects Versions: 5.0, 5.0.7, 5.0.8 Reporter: Chris Lewis Assignee: Howard M. Lewis Ship The PageRenderDispatcher and ComponentActionDispatcher each have to decipher the component or page being requested. The resolution of the associated class in each case is essentially the same. I'm working (again) on a transparent access control system that must do the same thing, so I've basically copy/pasted this logic. It would seem to make sense (and also be convenient for me) to centralize this logic somewhere - probably as a static method. This would also insulate code like mine against breakage.
