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.7, 5.0, 5.0.8
Reporter: Chris Lewis
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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
