On Jun 17, 2008, at 9:58 AM, Nick Stuart wrote: > Has anyone had the requirement to use more then one properties file > for defining field labels? We basically want the setup that > FieldLabels.properties is our 'default' settings that rarely ever > get change, and if our customers want to change field labels they > can in their own 'customer.properties' file. Right now I don't see > anyway to have this capability in Stripes. We did it in 1.4 by > changing the LocalizationBundleFactory interface and some of the > other supporting classes to take lists, but I would like to avoid > having to do this again with 1.5.
If LocalizationBundleFactory can be used to return any ResourceBundle, why not implement your own version of ResourceBundle that is aware of the hierarchy of property files? The ResourceBundle interface is pretty straightforward, and with a Factory to generate them (rather than relying on the default getResource routine), makes them even more flexible. The problems with ResourceBundles are the way they're located by default through the classloaders (which make it difficult to swap in your own ResourceBundle implementation). The Factory solves that. Regards, Will Hartung ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users
