LocalizedMap.java - Do we really need it?

[Adrian Crum]

I'm having a problem integrating the Unified Expression Language with 
the FlexibleMapAccessor class - due to that class supporting the 
LocalizedMap interface. The LocalizedMap interface is implemented in the 
MapStack class and it is used in only one place - GenericEntity.

Here's the thing - I can't think of any scenario where this kind of 
functionality would be needed. Where in the framework do we ever 
construct a MapStack with different elements for different locales? As 
far as I know, each MapStack instance represents a single locale. Am I 
wrong? If not, can we phase out LocalizedMap?

-Adrian