[
https://issues.apache.org/jira/browse/TAPESTRY-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543181
]
Howard M. Lewis Ship commented on TAPESTRY-1889:
------------------------------------------------
I'm really opposed to that kind of tight binding of pages. I still see it as
an action event on the page that rendered the link that, in code, invokes
methods on the target page. Maybe I'm being obstinate, but this approach seems
to open up the internals of the target page more than I'm comfortable with.
> Pull out component action event handling logic
> ----------------------------------------------
>
> Key: TAPESTRY-1889
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1889
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.6
> Reporter: Dan Adams
>
> ComponentActionRequestHandlerImpl.handle() has all the logic for triggering
> an event and then handling the return value. This should be pulled out and
> generalized so that you can trigger a custom event on another page and return
> the resulting ActionResponseGenerator. This could be useful if you have a
> page with an action link that when clicked fires a custom event on another
> page.
--
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]
