tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Massimo Lusetti (JIRA)" <...@tapestry.apache.org>
Subject [jira] Commented: (TAPESTRY-2464) Migrate Pattern logic to catch pageName, context, events and components from ComponentEventDispatcher to a service
Date Fri, 04 Jul 2008 13:29:46 GMT

    [ https://issues.apache.org/jira/browse/TAPESTRY-2464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12610579#action_12610579
] 

Massimo Lusetti commented on TAPESTRY-2464:
-------------------------------------------

BTW I've chosen to close this as "Later" cause i still think it would be nice to have this
logic as a utils/service but don't feel the need right now

> 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
>            Priority: Minor
>
> 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Mime
View raw message