Well, I now just assure all my Translators are also FieldTranslators and
vice versa.
Kind egards,
Joachim
Christoph Jäger wrote:
Hi,
I just stumbled upon the same problem when updating from 5.0.14 to
5.0.15. There must be a way that Tapestry automatically creates the
FieldTranslator if a Translator is specified for a field. All the
information should be there. As I see it, apart from the Translator,
the FieldTranslator needs the Field, a MessageFormatter and a
FormSupport instance to do its work. I can't believe we have to
"manually" pick up all of these objects and create a FieldTranslator
(a separate one for each field in a form). Looking at how Tapestry
automatically creates / converts / coerces lots of other useful stuff,
I am almost sure there are some magic configuration entries to enable
automatic creation of FieldTranslators (given a Translator), we just
need to find them.
Best Regards,
Christoph
On Oct 8, 2008, at 19:25 , Joachim Van der Auwera wrote:
Howard Lewis Ship wrote:
A FieldTranslator is a wrapper around a Translator that is configured
for a specific Field component.
Thanks.
Should these not be created automatically?
This has caused me major headaches for migrating to 5.0.15, I had to
change all my translators, assure they also implement FieldTranslator
and replace all translate="translate:string" to a (custom)
StringTranslator which implements both Translator and FieldTranslator.
Kind regards,
Joachim
On Wed, Oct 8, 2008 at 5:40 AM, Joachim Van der Auwera
<[EMAIL PROTECTED]> wrote:
And when should which be used?
I am getting coercing errors trying to convert between the two, but
it is
unclear to me why there is a difference (the interfaces look very
similar).
Joachim
--
Joachim Van der Auwera
PROGS bvba, progs.be
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Joachim Van der Auwera
PROGS bvba, progs.be
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Christoph Jäger
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Joachim Van der Auwera
PROGS bvba, progs.be
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
