You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Daniel Lydiard <dl...@hotmail.com> on 2006/03/03 19:53:41 UTC

Tacos ajax direct link

When i click on an AjaxDirectLink, I'm noticing in my log file that the 
whole page is being re-rendered in the background, then the small component 
i told AjaxDirectLink to update will update.

So everything works, it just seems inneffecient, especially when it's 
re-rendering my contrib:Table component when clicking on an Ajax link.

Am i doing something wrong, or is this more of a Tapestry limitation?

Thanks.

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


Re: Tacos ajax direct link

Posted by Jesse Kuhnert <jk...@gmail.com>.
It's a tacos limitation...Tapestry was never written with this requirement
being known :) It will be fixed ~hopefully~ in 4.1, and definitely in tap5.

On 3/3/06, Daniel Lydiard <dl...@hotmail.com> wrote:
>
> When i click on an AjaxDirectLink, I'm noticing in my log file that the
> whole page is being re-rendered in the background, then the small
> component
> i told AjaxDirectLink to update will update.
>
> So everything works, it just seems inneffecient, especially when it's
> re-rendering my contrib:Table component when clicking on an Ajax link.
>
> Am i doing something wrong, or is this more of a Tapestry limitation?
>
> Thanks.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>

Re: Tacos ajax direct link

Posted by Daniel Lydiard <dl...@hotmail.com>.
I have another quick question.

I have an AjaxDirectLink which can show/hide a div which contains form input 
components.  If the form inputs are visible and I then hide the box 
containing the form inputs then submit the form (regular tapestry submit)  I 
get null pointer errors everywhere, most likely because tapestry was 
expecting the components to be there.

Is there a good way around this?  The stack trace I get is pure tapestry 
engine calls and has nothing to do with my own code (not one reference to 
any of my packages)...

I guess I could always just set the div to hidden (via css), but the purpose 
was to save rendering time by not rendering the components at all when 
appropriate.

Thanks.

BTW keep up the work on Tacos, I'm really liking it, and it's very easy to 
use :)

----- Original Message ----- 
From: "Daniel Lydiard" <dl...@hotmail.com>
To: "Tapestry users" <ta...@jakarta.apache.org>
Sent: Friday, March 03, 2006 10:53 AM
Subject: Tacos ajax direct link


> When i click on an AjaxDirectLink, I'm noticing in my log file that the 
> whole page is being re-rendered in the background, then the small 
> component i told AjaxDirectLink to update will update.
>
> So everything works, it just seems inneffecient, especially when it's 
> re-rendering my contrib:Table component when clicking on an Ajax link.
>
> Am i doing something wrong, or is this more of a Tapestry limitation?
>
> Thanks.
>
> 

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