很容易找到getText實際的操作類是LocalizedTextUtil，方法public static String findText(Class aClass, String aTextName, Locale locale, String defaultMessage, Object[] args, OgnlValueStack valueStack)；
java doc 如下
Finds a localized text message for the given key, aTextName. Both the key and the message itself is evaluated as required. The following algorithm is used to find the requested message:
- Look for message in aClass' class hierarchy.
- Look for the message in a resource bundle for aClass
- If not found, look for the message in a resource bundle for any implemented interface
- If not found, traverse up the Class' hierarchy and repeat from the first sub-step
- If not found and aClass is a ModelDriven Action, then look for message in the model's class hierarchy (repeat sub-steps listed above).
- If not found, look for message in child property. This is determined by evaluating the message key as an OGNL expression. For example, if the key is user.address.state, then it will attempt to see if "user" can be resolved into an object. If so, repeat the entire process fromthe beginning with the object's class as aClass and "address.state" as the message key.
- If not found, look for the message in aClass' package hierarchy.
- If still not found, look for the message in the default resource bundles.
- Return defaultMessage
主要就是查找resource bundle，下面說明一下
1. 先查找該class（一般我們是在action調用，就是該action對應的class了）對應的properties文件，找不到再去找對應的接口，找不到再去從該class的繼承樹上去重復前面的步驟。
2. 如果是ModelDriver，以上找不到再以model的class去重復1的步驟
3.繼續(xù)找，如果key是符合ognl表達式還以ognl表達式去解析類，如果能找到類，還以以上的步驟去查找
4. 還找不到，就從根據package以及package的繼承樹去找，這還包括了該class的繼承樹所有的class的package樹（這一步存在了太多的重復查找工作，因為很多package都是相同的）
5 使用默認的resource bundle
java.util.ResourceBundle雖然有cache，但是ww為了減少調用getResourceBundle方法，也維護了一個miss的hashset，找不到的bundle name就丟進去，那么每一次查找都同步了這個miss，如果很多次查找，開銷也是很大的。
我就舉一個例子，就說第四步查找package樹好了
// nothing still? alright, search the package hierarchy now
for (Class clazz = aClass;
(clazz != null) && !clazz.equals(Object.class);
clazz = clazz.getSuperclass()) {
String basePackageName = clazz.getName();
while (basePackageName.lastIndexOf('.') != -1) {
basePackageName = basePackageName.substring(0, basePackageName.lastIndexOf('.'));
String packageName = basePackageName + ".package";
msg = getMessage(packageName, locale, aTextName, valueStack, args);
if (msg != null) {
return msg;
}
if (indexedTextName != null) {
msg = getMessage(packageName, locale, indexedTextName, valueStack, args);
if (msg != null) {
return msg;
}
}
}
}
假設你的action繼承樹是這樣
com.bba96.core.webwork.actions.DefaultActionSupport
com.xxxx.web.actions.XXXActionSupport
com.xxxx.web.user.actions.UserAction
com.xxxx.web.user.ViewUserAction
且不說ww沒有判斷是否是com.opensymphony.xwork.ActionSupport或者ww的接口就停止，光是自己的繼承樹，就是4+3+3+3=13次，再加上往上的繼承樹以及對應的接口，com.opensymphony.xwork.ActionSupport以及Action, Validateable, ValidationAware, TextProvider, LocaleProvider, Serializable, ContinuableObject的接口，查找次數超過30次甚至更多，這里的每一次都有一個同步miss的過程，開銷相當大。
如果你的key所在的resource bundle沒有對應到合適的class或package時，例如說放在了default bundle中，ww會浪費很多時間。這種情況下，我在沒有并發(fā)的時候測了一下，一次getText大概耗時40ms左右
所以在實際應用我們應該避免這種情況出現，要不讓resource bundle一一對應class，要不就自己實現一個簡單的getText，其實要是ww的ActionSupport的textProvider允許改變就最好了。