> What is the use case that drives this change?
> Is it the ability to change the view mapping?
For me it's just that. And not only change but adding new mappings without restarting the server. And as you say:
"Checking for the view change and then dumping the view cache and reloading would be pretty easy."
So why do you not want to do just that? I hate to restart my server everytime I need to add a new mapping or change the existing. It's slow and involves more steps than should be needed (e.g. ssh connection to the server - stop container - start container - exit) instead of just clicking one link that does the whole job as it is implemented in Struts' default reload.do action (it loads all the mappings and all the properties files).