Hi,
I am not very CSS savy Thiago, but I think center is code efficient vs the css
way?
Please see my previous response to Lance as to why I am resisting your
suggestions. In short it is not OO, DRY or to the Tapestry ethos.
IMO Tapestry framework should take care of persisting component parameters
between requests. Just saying ;)
John
----- Original Message -----
From: Thiago H de Paula Figueiredo
To: Tapestry users
Sent: Friday, December 06, 2013 11:28 AM
Subject: Re: component paramter frustrations
On Thu, 05 Dec 2013 21:53:44 -0200, John <j...@quivinco.com> wrote:
> here is the template with the problematic actionlink highlighted
Thanks!
> <center>${message:text.diarydenied}</center>
I haven't seen the very deprecated <center> HTML tag for many years . . .
I felt like in 1998 when I read it. :P
> <a t:type="actionlink" t:id="bardayClickedLeft"
> t:zone="dateZone" t:parameters="parms" href="#" class="daybarnavl"
The 'parameters' parameter of ActionLink and EventLink doesn't work like
you think. As its documentation says, it adds the map as *query
parameters* (a=b&c=d) in the URL, and this is completely unrelated to
component parameters, which are passed from other components or pages. If
you want to get these values back from query parameters, you must use
@RequestParameter or Request.getParameter() or, better yet, don't use
query parameters and do what Lance said and use the 'context' parameter of
ActionLink and EventLink.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
Help me spend a whole month working on Tapestry bug fixes and
improvements: http://igg.me/at/t5month
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
