There were an activity in Avalon scratchpad a while ago on the i18n resources abstractization, but AFAIK it was never finished. The idea was to have a Bundle interface and use any implementation you like: a property file, XML file or a database. Also, you could use different factories for your bundles, say use a property file that is loaded from a DB, JNDI and so on.
Current implementation of XMLResourceBundle is the first implementation from the Avalon scratchpad. I know that the approach in i18n transformer is very limiting, but since nobody complained about it before (except for the superfluous logging) I've never care about it. Btw, I don't think that replacing XMLResourceBundle with a HashMap will improve perfomance much in the long run, because the values are stored in a HashMap on the first use, so there should be no much difference. I've redesigned i18n samples and now working on the documentation to attract more people to use it and therefore more people will be interested to improve it. But the time is everyone's problem... Konstantin ----- Original Message ----- From: "Torsten Curdt" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, May 21, 2002 10:44 PM Subject: Re: I18n Performance > > But IIRC the I18nTransformer is still not cachable - is he? > > doh! Yes, you're correct. (I'm using my own bastardization of the standard > I18nTransformer over here. Cacheable + very fast since i replaced the > XMLResoruceBundles with some hashmaps. Its on my list to package up + > donate back, time is just very very slim :( Same here *sigh* Ages ago I proposed some changes on having a more abstract resource bundle (we'd like serve our from db) which has a last modified stamp so we can easily implement cacheable... but time you know ;-) This would be a major(!) improvement... we haven't yet (and wouldn't) use the i18n transformer under the current circumstances. My 2 cents -- Torsten --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]> --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
