[
https://issues.apache.org/jira/browse/TAP5-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15028331#comment-15028331
]
Jochen Kemnade commented on TAP5-2225:
--------------------------------------
That sounds like a more sophisticated approach, but might be a little more
complicated to use. Should the module really check which events are handled? We
do that server-side anyway and currently, you can also create an eventlink for
an event that is not handled.
Do you have an idea how you could create an event link for an embedded
component? I cannot think of a solution where you wouldn't have to pass the
component's id.
By "non-nested pages"; I meant those that are not in a "subdirectory". That
might work but I haven't tested it so far.
> Create client-side API to call a component's event handler methods
> ------------------------------------------------------------------
>
> Key: TAP5-2225
> URL: https://issues.apache.org/jira/browse/TAP5-2225
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.4
> Reporter: Jochen Kemnade
> Assignee: Thiago H. de Paula Figueiredo
> Labels: ajax, event, handler, javascript
>
> It should be possible to create URLs for components' event handlers on the
> client side.
> There could be a function that mirrors the behavior of
> ComponentResources#createEventLink. It might be passed an event name or an
> object with additional information such as a page name, a request context, or
> additional request parameters.
> The function could either return the URL or a function that makes an XHR and
> passes the response to a callback.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
