You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Erich Gormann <e....@gormann.de> on 2014/04/15 13:59:16 UTC
Tapestry render variable in zone is null
Hi there,
I'am new to that list and want to say hello to every one here.
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. The client side zone id is calculated from a hard
coded prefix and suffix taken from one of the render variables properties,
lets say the id.
Page rendering works fine if page is called via noral http request. Zone
update is triggered by an onValueChange event fired by a select component
contained inside the zone. And now things get weird. The render variable
used to build the zones client id seems to be null after the ajax request.
Coding it without a form around the loop and replacing the select by an
event or action link works fine.
Currently I have no further idea. Any help is appreciated.
Regards
Erich
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Tapestry render variable in zone is null
Posted by Erich Gormann <e....@gormann.de>.
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"
<th...@gmail.com> wrote:
> On Tue, 15 Apr 2014 08:59:16 -0300, Erich Gormann <e....@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
Re: Tapestry render variable in zone is null
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Tue, 15 Apr 2014 08:59:16 -0300, Erich Gormann <e....@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.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org