Message Boards

How to configure the portlet to use the Language_forCustomer.properties ?

majdi Achouri, modified 3 Years ago.

How to configure the portlet to use the Language_forCustomer.properties ?

Junior Member Posts: 38 Join Date: 11/21/19 Recent Posts
Hello

I have an authentification MVC Portlet which it will be deployed on many Customer server so the idea behind is to customize the labels (keys) in the (login.jsp, create_account.jsp...) and put the labels specified by each customer. 

Version: Liferay 7

The idea is to use the Language_xxx.properties to specify the (key, Value) which will be printed in the interface of each customer. 

For example I have 3 customer, So I need here 3 properties file : Language_forCustomer1.properties, Language_forCustomer2.properties , Language_forCustomer3.properties thats needs to be putted under /resources/content/ .

I need a solution for each deploy to each server, Example to deploy to the customer 1 server, I need to configure the app to take the Language_forCustomer1.properties and read the labels from there. 

How could I achieve this config( maybe with xml) ? Maybe somebody has an idea ans could help!
Thanks in advance
thumbnail
Olaf Kock, modified 3 Years ago.

RE: How to configure the portlet to use the Language_forCustomer.propertie

Liferay Legend Posts: 6403 Join Date: 9/23/08 Recent Posts
majdi Achouri:

The idea is to use the Language_xxx.properties to specify the (key, Value) which will be printed in the interface of each customer.
While you'd end up with different Language.properties anyway, I'd organize them in a different way than you propose:
You can override translations for each module from another module - the original module doesn't need to be a Liferay core module for that. So you can write your original portlet and provide it with a generic translation, then have 3 more projects, each with a customer specific translation that overrides the original module's translation. You'd end up delivering one of these 3 projects to each customer - name the modules by customer, and you'll easily have an overview over what goes where, and are 100% on the beaten paths, no extra code, great maintainability.