[prev in list] [next in list] [prev in thread] [next in thread] 

List:       tapestry-user
Subject:    Re: Ajax and Component's inside Zones
From:       Casey Link <casey () outskirtslabs ! com>
Date:       2015-06-16 8:22:03
Message-ID: 2161493.vYsxQx0WH2 () dhcppc8
[Download RAW message or body]

On Thursday, June 11, 2015 09:24:00 AM Thiago H de Paula Figueiredo wrote:
> On Thu, 11 Jun 2015 07:45:06 -0300, Casey Link <casey@outskirtslabs.com>  
> wrote:
> 
> >  <a t:type="actionlink" t:id="removeItem" context="item.id">
> 
> ActionLink and EventLink are not supposed to do AJAX requests without a  
> zone parameter, so I really don't know how they made AJAX requests in your  
> case. Try adding zone="^".
> 
Super. This was what I needed.

> > 2. I've tried using an eventlink instead of an actionlink, but clicking  
> > it still causes a full page refresh
> 
> EventLink and ActionLink are almost the same, me considering ActionLink to  
> be mostly deprecated, so use EventLink instead and to handle it, just use  
> on[event name](). If you use on[event name]From[component id], the event  
> handler will only work in the class associated to the template where the  
> component was declared, because component ids are local to where they were  
> declared. ActionLink always uses the same event name, so you end up  
> needing to use the component id in the event handler method name or  
> @OnEvent annotation.

Great. I've migrated to EventLink. Thanks for the tips!

Casey

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org

[prev in list] [next in list] [prev in thread] [next in thread]