There is already an interface: MessageResolver Just providing an @Alternative should be perfectly enough!
LieGrue, strub ----- Original Message ----- > From: Nicklas Karlsson <[email protected]> > To: [email protected]; Mark Struberg <[email protected]> > Cc: > Sent: Sunday, October 7, 2012 3:41 PM > Subject: Re: proposal for JSF Messages > > It's pretty trivial to @Specialize the resolver and inject an entity with a > cached Map<String, String> from the DB. > > Like Mark said, it would probably be possible to generalize fetching from a > flat file with (key, value, locale) rows but it's probably not worth the > while when custom implementations are that simple to write. > > Still trying to sell the MessageSource interface so you wouldn't have to > @Specialize the resolver to get away from the properties files ;-) > > On Sun, Oct 7, 2012 at 2:40 PM, Mark Struberg <[email protected]> wrote: > >> Yes, just provide your own MessageResolver as @Alternative. >> >> I think Nicklas Karlson already implemented a database backed version. >> I'm not sure we can add it to DS itself as the database schema is > usually >> different for each company. >> >> LieGrue, >> strub >> >> >> >> >> ----- Original Message ----- >> > From: Thomas Andraschko <[email protected]> >> > To: [email protected] >> > Cc: >> > Sent: Sunday, October 7, 2012 1:14 PM >> > Subject: Re: proposal for JSF Messages >> > >> > Will it also be possible to use the messages stuff without properties? > We >> > always have our translations in the database. >> > >> > > > > -- > Nicklas Karlsson, +358 40 5062266 > Vaakunatie 10 as 7, 20780 Kaarina >
