What are Resource Bundle Best Practices techniques for Enterprise App?
Regarding JDeveloper: 11.1.1.6.0, Studio Edition
I was wondering if someone could provide advice on Best Practices for managing Resource Bundles for an international Enterprise Application.
I have been reading textbooks and throughout the web, and I can find different options available. And I can find cautionary tales to get it right at the beginning of Development, but I cannot find Best Practices suggestions.
For instance:
- Should I use XLIFF Resource Bundle, Properties Bundle, or List Resource Bundle?
- What are the benefits and disadvantages of storing the Key/Value pairs in the database?
- It seems that storing in the db would make maintenance easier, because applications do not need to be redeployed, but would they be slower?
- One textbook indicates that "One Bundle per Project" is preferred for ViewController Project, and "One Bundle Per File" is preferred for Model Project. However, I cannot help but think if the whole Enterprise used just one Resource Bundle, it would save typing cust_id/Customer Number in 10 different Bundles.
- One text indicates how to maintain translated versions of Access Keys, if the Bundle is a Properties Bundle, but provides no assistance for other Resource Bundles.
Advice regarding Best Practices would be quite helpful.
Sincerely,
Arie