For the record, I use a global .properties file to contain all common
application strings. I avoid page/component properties files because I
feel they cause too much scatter. The exception being if a component (or
collection of them) merits its own library, then I'll make an exception.
Correct m
Because the model classes (non T5 components/pages/mixins) are not
auto-reloaded when changed, validation put into business objects with
attributes will require a restart of the server when altered. Many
people put them into .properties files so that they can benefit from
the rapid reloadi
Obviously it depends on whether you will ever need to do l10n.
The validation examples don't do it to keep the code shorter.
Otherwise of course it makes sense every string is localizable.
Whether you do it globally or per page/component is up to you.
Cheers,
Nick.
Robert A. Decker wrote:
I'm
