Em Sun, 27 Dec 2009 12:43:29 -0200, Bryan Lewis <jbryanle...@gmail.com>
escreveu:
I'd like to see either or both of the techniques.
Me too. It's nice to have some different approaches to the same problem
and them pick the one that suits better a given scenario.
I thought that it wasn't
possible to override Tapestry's built-in translators. (See TAP-725, "You
cannot define two different translators for a single field type.")
As of 5.1.0.5, it isn't possible to override them for a given type
globally, but you can override it in a given TextField instance (translate
parameter).
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, software architect and developer, 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
