Question

Consider the following class DialgBean.java, which defines the properties of a dialog box on a web page. Below is the class and its bean definition

public class DialogBean{
  private int height;

  public void setHeight(int height)
  ...
}

<bean id="dialogBean" class="org.springhelp.DialogBean">  
 <property name="height" value="${dialogBean.height}"/>
 ...
</bean>

From the above example you can see that the DialogBean’s height property is being fetched by a PropertyPlaceholderConfigurer.

The problem is that the application I am working on supports multiple clients, and most clients have separate requirements for the height parameter of a dialog box. Therefore, I can not simply pull the height parameter from one properties file.

So, how do I inject a client specific height parameter into a DialogBean using the bean definition described above, where the client id is stored as the variant in the java.util.Locale object?

Is there a way to pass to a custom bean factory post processor run time data like the Locale?

Answer 1

The simpler, but more cumbersome solution, is

• declare one bean per local variant and extend from a parent (base) bean.
• create a thin wrapper for the BeanFactory that accepts the Locale
• upon lookup for a Locale based bean, the wrapper creates bean name options from the parent (base) bean name and the Locale
• traverse over the list of bean defintion names and find the first one that matches the list of created name options.

Of course, the list of options have to be in order of priority.