[TAPESTRY-2464] Migrate Pattern logic to catch pageName, context, events and components from ComponentEventDispatcher to a service

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Later
• Affects Version/s: 5.0
• Component/s: tapestry-core
• Environment: Any
• Assignee: Unassigned
• Reporter: Massimo Lusetti
• Created: 18/Jun/08 14:06
• Updated: 04/Jul/08 13:29
• Resolved: 04/Jul/08 13:28

Description

It would be great if the logic (Pattern) inside the ComponentEventDispatcher which match the activePageName, events, contexts and components would be extended a little bit and refactored out to a service or more probably a utils method.

This way it could be used by various other dispatcher as well.

Issue Links

• is related to: TAPESTRY-2025 Centralize page/component class resolution logic