翻译硬编码字符串的最佳做法

Question

I have a finite set of strings for a product name. I also have a web service which sends one of these product names. However I need to send the product name in another format.

So I need a formatter/mapper somewhere before I send the message.

I COULD just make some hardcoded mapper class which takes in an argument and returns a hardcoded string like this:

String mapper(String productName) {
    switch (productName) {
    case "product1":
        return "prod1";
    case "product2":
        return "prod2"
}

However, I dont really like this approach, but I have a hard time trying to think up a better solution. Anyone have a better solution for this problem?

I'm considering storing the mapping in the database and then create a DAO for this mapping which instead of using a switch it uses the argument as key and then queries the database which returns the alternative product name, but I'm not sure if its really a better solution.

any thoughts?

* EDIT *

Forgot to mention this:

The original product names are currently stored in the database. I will need to translate these names without modifying the current code/table setup, ie I cannot edit the table and current classes, but I can create new tables/classes if needed.

Answer 1

How about using properties file having content like

product1=prod1 
product2=prod2

and your method..

{
   //initializer
   Properties props = new Properties();
   props.load(...);
}

String mapper(String productName) {
   props.getProperty(productName);
}

Answer 2

Use an enumeration (or set of integers) as ID for product 1, 2 etc.

Then use a dictionary/map/array/whatever or a get function to get the name (either "product1" or "product2"). Do not use strings when you want to USE these types, becasue they tend to occur more than one time in your code and if you forget to change it at one location you get inconsistencies.

Answer 3

Using the database is a flexible approach, giving you the opportunity to adapt the mapping at any time, without restarting anything. However, performance may be of concern in that case. If so, build a cache of the complete mapping table and set up a regular refreshing schedule for it.