This week's book giveaway is in the General Computing forum. We're giving away four copies of Arduino in Action and have Martin Evans, Joshua Noble, and Jordan Hochenbaum on-line! See this thread for details.
In my current project the requirement is that the same web application should support multiple brands. Each brand will have its unique domain name. E.g. brand-a.com,brand-b.com etc. There is only one web application instance which supports all the brands. In order to do this it was decided that there will be one resource bundle per brand & I18n version of resource bundles will exist for each brand.
Brand-A has Messages_brandA.properties, Messages_brandA_en.properties, Messages_brandA_fr.properties, Messages_brandA.properties_es etc.
Brand-B has Messages_brandB.properties, Messages_brandB_en.properties, Messages_brandB_fr.properties, Messages_brandB.properties_es etc.
The system also has one default brand. and corresponding resource bundles.
We are using different APIs like displaytag jar, velocity API etc.
Please provide me with some concrete information with which I can go ahead with approach.
First off, Ease Up. We're all volunteers who answer questions in our spare time.
Second, the web site I maintain has similar functionality: See here and then here and then here. We didn't use resource bundles. We have an XML-based approach. We have a configuration file like this (this snippet shows the configuration for the logo on the left-hand side of the page, note the "default" value with no qualifier):
When the application is loaded, these XML files are loaded into a map (by key) of maps (by qualifier). We then have several classes to access these values in code and on JSP pages. Specify the key and qualifier and get whatever value is in the XML. It's very flexible in practice.
I've much simpler configurations with property files, where each property had an additional value indicating the environment (see here). nothing as convoluted as the above.
I honestly don't know if it is possible to do what you want with plain message bundles. It's always a good idea to test the feasibility of a design before committing to it.