You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Dan Adams (JIRA)" <de...@tapestry.apache.org> on 2007/11/07 15:31:53 UTC
[jira] Created: (TAPESTRY-1889) Pull out component action event
handling logic
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Closed: (TAPESTRY-1889) Pull out component action event
handling logic
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAPESTRY-1889.
------------------------------------------
Resolution: Invalid
Assignee: Howard M. Lewis Ship
I think the original context of this has changed; for example, ActionResponseGenerator is gone.
I think you could get a page, cast it to Component, get its ComponentResource and then navigate its component hierarchy and invoke triggerEvent().
> 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
> Assignee: Howard M. Lewis Ship
>
> 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-1889) Pull out component action event
handling logic
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org