ViewResolvers exist to allow Controllers (you are using Spring Controllers aren't you ?) to specify views by logical names rather than physical url's directly. This makes it much easier to refactoryour UI code or to change the type of view you want to render, say from JSP to PDF. If you make a change, you won't have change the Controller, just the mapping.
InternalResourceViewResolver is a subclass of UrlBasedViewResolver that supports JSP's. UrlBasedViewResolver can map view names to views without having to supply an explicit mapping. You can just use naming conventions to do the mapping. ResourceBundleViewResolver is very convenient if internationalization is needed or may ever be needed. The
Java ResourceBundle class javadoc has more info regarding internationalization naming conventions. Spring's ResourceBundleViewResolver provides support for those file naming conventions.
The Spring javadocs and reference documentation are really very good andprovide much more detail about this and other issues than I can.
You should try reading them.
kktec<br />SCJP, SCWCD, SCJD<br />"What we observe is not nature itself, but nature exposed to our method of questioning." - Werner Heisenberg