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

                 Key: TAPESTRY-2464
                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2464
             Project: Tapestry
          Issue Type: Improvement
          Components: tapestry-core
    Affects Versions: 5.0
         Environment: Any
            Reporter: Massimo Lusetti


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.

-- 
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]

Reply via email to