Hi,
Is changing the property label (on the page's properties file) on
Grids/BeanDisplays/BeanEditForms so bad? I believe this auto-naming just do the
majority work... And when you need to support another languages also, it's more
usual to change it...
Usually, if you name your Objects/Properties well, the auto naming would be
better... That would be a problem only if you were working on infra-structure
classes that couldn't be changed...
But i'm curious to know if i can define the property's name in another way than
properties/beanmodel
________________________________
De: kamiseq <kami...@gmail.com>
Para: Tapestry users <users@tapestry.apache.org>
Enviadas: Terça-feira, 26 de Janeiro de 2010 11:17:07
Assunto: message catalog and generated labels from property name
hi,
my problem is that tapestry in components generates labels as two words
(with space between) from property name when camel notation is used
so property name like rtobjectDescr will be changed to 'Rtobject Descr' and
then I cant change this in my message catalog to something that makes more
sense to a user.
and I can really find a solution to that other then add another getter and
setter with other name and exclude original name in component
thanks
pozdrawiam
Paweł Kamiński
kami...@gmail.com
pkaminski....@gmail.com
______________________
____________________________________________________________________________________
Veja quais são os assuntos do momento no Yahoo! +Buscados
http://br.maisbuscados.yahoo.com
