[TAPESTRY-2025] Centralize page/component class resolution logic

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 5.0, 5.0.7, 5.0.8
• Component/s: Framework, tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Chris Lewis
• Created: 06/Jan/08 00:49
• Updated: 23/Jun/08 14:22
• Resolved: 24/Feb/08 02:45

Description

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.

Issue Links

• relates to: TAPESTRY-2464 Migrate Pattern logic to catch pageName, context, events and components from ComponentEventDispatcher to a service