Provide feature to plug custom ResourceBundle implementations into Click.
I think we should call this ResourceBundleService. "MessageMap" doesn't provide enough context as a service name. It sounds as if it has something to do with messaging (JMS) rather than localization. ResourceBundle on the other hand, is quite obvious.
Of course we still create a MessagesMap instance.
> I'm not sure MessageMapService is the right name but can't think of something better at the moment.
In the DTD, there's:
log-service, resource-service, template-service
So to be consistent, maybe to name it simply "message-service" ?
This looks great, exactly what I had in mind. Just to expand a little on the use cases where a custom messages map is useful:
I'm not sure MessageMapService is the right name but can't think of something better at the moment. We can refactor it at a later stage so feel free to commit.
Attached is my take on the messages map service. The messages map that page & control holds is just a Map<String, String> and my DefaultMessagesMapService return instances of the MessagesMap which is the default implementation of the Map<String, String>.
Let me know if you had something entirely different in mind.