On Fri, 24 Sep 2010 15:22:50 -0300, Michael Taylor <miketay...@google.com>
wrote:
Thanks Thiago!
You're welcome!
So for the record I had to
1. In my SetupRender method I assign the parameter value to a property
foo of the component.
I can't see why you need this.
2. Made my onActionFromRefreshZoneLink method take a context parameter
which
I also assign to the same component property.
3. Add a t:context attribute to my action link similar to
<a t:type="actionlink" t:id="refreshZoneLink" href="#"
*t:context="${foo}"*t:zone="theZone">Refresh</a>
Never ever use an expansion (${}) when passing parameters, as it forces a
conversion to String before passing the value to the component parameter.
4. Modify my data fetching to use the value from the component property
foo instead of using the parameter value directly.
In this way I can get the id from the parameter on the initial render and
from the action link context on the subsequent ajax refreshes.
Not sure if this is the cleanest solution, but it seems to work.
I haven't seen your code, so I can't say if there's a better solution.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
