Hi all,
Thanks for the pointers. In the end I switched to AjaxResponseRenderer
rather than returning the zone's body, and all seems to work well. I'm
not sure why I didn't do it this way to begin with. You can see the old
line of code now commented out.
public void onFilter(){
expa
You can have it easier in Tapestry 5.4.2+, not having to pass the event URL
from Java to JavaScript. From the example at
tapestry.apache.org/ajax-and-zones.html#AjaxandZones-Invokingserver-sideeventhandlermethodsfromJavaScript,
supposing you want to trigger a server-side event when clicking the el
On Thu, Dec 13, 2018 at 11:04 PM Christopher Dodunski <
chrisfromtapes...@christopher.net.nz> wrote:
> Hi all,
>
Hello!
> I had mistakenly thought that any event handler method could render a
> response through return type, whereas seemingly this is unique to events
> triggered by Tapestry's ac
That's actually quite easy:
define(["jquery", "t5/core/utils", "t5/core/ajax", "t5/core/events"],
function($, utils, ajax, events) {
return function(spec) {
var $zoneElement = $('#' + spec.zoneElementId)
$zoneElement.trigger(events.zone.refresh, { url: spec.zoneRefreshUrl })
Hi all,
I had mistakenly thought that any event handler method could render a
response through return type, whereas seemingly this is unique to events
triggered by Tapestry's actionlink, eventlink and form components.
I developed a filter pane component for limiting the number and (date)
range of
