|
From: Darren D. <da...@da...> - 2005-09-21 10:34:07
|
Hi all, The "redirect:" prefix that was added as a feature last year enables controllers to remain ignorant of the redirect since the String value containing the prefix can be injected into the controller bean. That much I understand. What I'm wondering is whether there was another benefit, or problem solved,= by taking this route? It seems to be a natural limitation of the choice of ViewResolver that the problem actually solves.. if the app is using a UrlBasedViewResolver or subclass, the redirect: prefix is needed. However, if the app defined an [Xml|ResourceBundle]ViewResolver and ordered= it first, then that could be used to resolve redirect views, falling back to t= he UrlBasedViewResolver for everything else. It looks like this would mitigate the need for the special handling of view name prefixes. I can't see anything in the discussions or JIRA issues from around the time this feature was added eluding to this other than a comment I made myself [= 1], so am I missing something here? [1] http://opensource2.atlassian.com/projects/spring/browse/SPR-387 Regards, --=20 Darren Davison Public Key: 0xDD356B0D |