Thomas Herzog <[email protected]> hat geschrieben:@All
Wouldn't it be fine to use convention over configuration within i18n module at
property keys definition via @MessageTemplate?
I read the user doc and it did not mention it.
Also the oportunity to define a alternativ property file location would be
fine, and to define the supported locales.
// As in cal10n, Different location for properties file.
@Base("META-INF/messages")
// As cal10n, supported locales, shall be evaluated, if files are present.
@Locales({@Locale("de_DE"), @Locale("en_US")})
class MessageHolder () {
// Would resolve to property key: MY_KEY
Strin getMyKey();
String myKey();
// Overwrites convention
@MessageTemplate("ERROR_USER_WRONG")
String getErrorForWrongUserDetected()
}
Would you aggree?
Is that already possible to define different location of the properties file
and that method names get resolved to property keys without annotation?
One question more, is it possible to access the implementation of the message
resource via EL within the view?
