All, Umm... I probably should have noticed this long before today, but I just observed a problem with my configuration and I wanted to make sure that my (new) understanding of the DateTool is correct.
So, I had DateTool configured to be an "application" level tool. That appears to have been a mistake. What I just observed is that the first user to trigger the creation of the DateTool tool ends up permanently-setting the locale for the tool to their preferred locale. Whoops. So the solution should be simply to change the "scope" of the tool from application to session, right? I should have realized that DateTool wasn't tied to the servlet API in any way, so sniffing the locale from the request (which is what I expected) is not really a possibility. Duh. Thanks, -chris
signature.asc
Description: OpenPGP digital signature
