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

List:       tapestry-user
Subject:    Re: Tapestry render variable in zone is null
From:       Erich Gormann <e.gormann () gormann ! de>
Date:       2014-04-15 13:52:38
Message-ID: 2c32ec1becebc6049c07528b3203cce6 () greatweb8 ! greatnet ! de
[Download RAW message or body]

Hi Thiago, 

Ok, I see, thanks a lot.  Meanwhile I restored the render variable by
reloading it using the value handled over in the select to the valueChanged
event - and now it works pretty good!

Regards
Eric

On Tue, 15 Apr 2014 10:26:45 -0300, "Thiago H de Paula Figueiredo"
<thiagohp@gmail.com> wrote:
> On Tue, 15 Apr 2014 08:59:16 -0300, Erich Gormann <e.gormann@gormann.de> 

> wrote:
> 
>> Hi there,
> 
> Hi!
> 
>> Problem description: I'am working with a tapestry form containing a loop
>> iterating over a bean collection. Inside the loop component a zone
>> component is nested.
> 
> Loop variables are no stored between requests nor they should. You should
 
> pass the appropriate information on the second request (the AJAX one) so 

> you can restore the needed state. Unfortunately, Select doesn't have a  
> context parameter yet as EventLink does, so, until then, you'll need to  
> write some custom JavaScript instead of relying on the one provided by  
> Select itself.

---------------------------------------------------------------------
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]