tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Kemnade (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-2225) Create client-side API to call a component's event handler methods
Date Wed, 09 Mar 2016 11:54:40 GMT

    [ https://issues.apache.org/jira/browse/TAP5-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186988#comment-15186988

Jochen Kemnade commented on TAP5-2225:

A problem I'm currently facing with my implementation is that event context needs to be encoded
so that {{URLEncoder}} can decode them. For example, just sending an ä as an ä will lead
to an exception. See also TAP5-539 and TAP5-1803.

> 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

View raw message