Dear List,
when an application uses a custom TextProvider it seems not to be used for validation errors. And if an Action is ModelDriven it behaves different again. Here is a sample app for that: https://github.com/wolpi/struts2-samples/tree/master/modeldriven-and-textprovider This sample has these Objects on ValueStack: - Model - CustomTextProvider - Action - DefaultTextProvider In hello.jsp three texts are shown: - Just a normal text via <s:text>. That text is resolved via CustomTextProvider (as expected). - A validation error of an action member. That text is resolved via the action itself, what I would not expect. - A validation error of a model member. That text is tried to be resolved via DefaultTextProvider, what I would not expect either. Am I doing something wrong here? Regards, Christoph This Email was scanned by Sophos Anti Virus
