Introducing Spring Framework

Chapter 6 ■ Using Resource Files
public void setPassword(String password) {
this.password = password;
}
public boolean isAuthorized(String email, String pass){
if(username.equals(email) && password.equals(pass))
return true;
return false;
}
}
As you can see in Listing 6-12, this login and its implementation are trivial for the example you want to do, just do
a basic authorization logic by passing an e-mail and password to the isAuthorized method and returning true if the
both parameters are equal to the injected properties. For now that’s all you need.
Next, let’s add your support class and its bean definition to your XML file, the org.springframework.beans.
factory.config.PropertyPlaceholderConfigurer class. See Listing 6-13 for your XML configuration file.
Listing 6-13. mydocuments-login-context.xml
In Listing 6-13, you are using the PropertyPlaceholderConfigurer. This class helps to externalize properties
values and keep them separate from your XML configuration files. These files follow the Java properties convention
and they are useful for customized environment-centric applications by adding values such as password, database
URLs, etc. During runtime, the PropertyPlaceholderConfigurer will take the metadata from the properties file and
replace it where a placeholder is specified. The placeholders have the form of a ${property} format.
In Listing 6-13, the property username will have the value test@mydocuments.com because it was replaced by
using the placeholder ${user.email} matching the property file (see Listing 6-9).
Now, let’s create your unit test for this change (see Listing 6-14).
69