Yep, we discussed that a while ago. IIRC there was some debate about how the message keys should look. Today we have short strings (e.g. "K1234") and there was a proposal to make that <module>.<id> (e.g. "beans.42"). I recall some objections to that proposal but cannot recreate them right now.
We didn't go on to discuss the Eclipse technique of using a Message type with fields for the messages. Regards, Tim Alex Blewitt wrote: > Not sure if it's particularly relevant, but the piece on Eclipse > performance bloopers is a good read: > > http://www.eclipse.org/eclipse/development/performance/bloopers.html > > Specifically, it mentions items to do with using string keys, the > dangers of using substring() and why they created their own binding > from messages-to-keys framework instead of using the standard Java > property list. > > Alex. > > On 31/05/06, Tim Ellison <[EMAIL PROTECTED]> wrote: >> I meant that the mechanism we currently have in LUNI (i.e. a resource >> file of externalized strings and a helper class like Msg to load the >> string and format it etc.) can be duplicated in each module that has >> externalized strings e.g. for exception messages. Of course, each >> module would only have its own messages. > > --------------------------------------------------------------------- > Terms of use : http://incubator.apache.org/harmony/mailing.html > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Tim Ellison ([EMAIL PROTECTED]) IBM Java technology centre, UK. --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
