Translate field names on validation

Nik · **Joined:** Wed Oct 15, 2003 4:40 pm **Posts:** 67

Hello and pardon my noobishness, but:

What is the most elegent way be to translate the field name also when validating?

if I have a field called "username" that can't be null then I can probably have a

Code:

validator.notNull=Can't be null. Nope.

and probably a

Code:

validator.notnull={propertyName} can't be null. Nope.

which would result in "username can't be null. Nope."

But how can you make a "second pass" through a resource bundle to translate the field name? Something like

Code:

validator.notnull=#{messages['{propertyName}']} can't be null. Nope.

emmanuel · **Posted:** Fri Aug 03, 2007 2:25 pm

That's an interesting subject, we are looking into in in the 303 expert group. But if you expect to expose that to your GUI, I find it awkward to use the field name.

Nik · **Joined:** Wed Oct 15, 2003 4:40 pm **Posts:** 67

emmanuel wrote:

That's an interesting subject, we are looking into in in the 303 expert group. But if you expect to expose that to your GUI, I find it awkward to use the field name.

Yes, with all i18n and resource bundles, it is shame if that "username" haunts you through all the languages without a possibility to look it up somewhere.

It can probably be worked around by manually taking the field name from the InvalidValue and running it manually through some bundles but it would be nice to have some automation (and seam integration)