So don't contribute your translator.
Instead, supply the translator directly to the translator parameter,
and construct it yourself?
The TranslatorSource is meant to be exactly that: a general source for
translators, so you don't have to constantly specify them yourself.
But if you have specific needs for specific fields, you should
manually supply your custom translator to those fields (and /not/
contribute it to TranslatorSource).
Robert
On May 28, 2009, at 5/289:21 AM , Lukasz Jazgar wrote:
2009/5/28 Thiago H. de Paula Figueiredo <thiag...@gmail.com>:
2009/5/28 Łukasz Jazgar <lukasz.jaz...@gmail.com>:
As Igor pointed out, it's not a bug, it's how things are. You can't
provide more than one default translator for a given type.
I don't want to provide more than one DEFAULT translator. Of course
more than one default translator for one type has completly no sense.
I want only to provide translator which translates to/from given type,
not default.
On the
other hand, you can provide a translator using the translate
parameter
of TextField, so the default one is not used in this case.
The probem is translator which I provide becomes default translator
and all TextField values are translated by him, regardless of
translate parameter.
Lukasz
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
