public class BeanNameViewResolver extends WebApplicationObjectSupport implements ViewResolver, Ordered
This resolver can be handy for small applications, keeping all definitions ranging from controllers to views in the same place. For normal applications, XmlViewResolver will be the better choice, as it separates the XML view bean definitions into a dedicated views file. View beans should virtually never have references to any other application beans - such a separation will make this clear.
This ViewResolver does not support internationalization. Conside ResourceBundleViewResolver if you need to apply different view resources per locale.
Note: This ViewResolver implements the Ordered interface to allow for flexible participation in ViewResolver chaining. For example, some special views could be defined via this ViewResolver (giving it 0 as "order" value), while all remaining views could be resolved by a UrlBasedViewResolver.
|Modifier and Type||Field and Description|
|Constructor and Description|
|Modifier and Type||Method and Description|
Return the order value of this object, with a higher value meaning greater in terms of sorting.
Resolve the given view by name.
getServletContext, getTempDir, getWebApplicationContext, initApplicationContext, initServletContext, isContextRequired, setServletContext
getApplicationContext, getMessageSourceAccessor, initApplicationContext, requiredContextClass, setApplicationContext
public void setOrder(int order)
public int getOrder()
Normally starting with 0, with
indicating the greatest value. Same order values will result
in arbitrary positions for the affected objects.
Higher values can be interpreted as lower priority. As a consequence, the object with the lowest value has highest priority (somewhat analogous to Servlet "load-on-startup" values).
public View resolveViewName(java.lang.String viewName, java.util.Locale locale) throws BeansException
Note: To allow for ViewResolver chaining, a ViewResolver should
null if a view with the given name is not defined in it.
However, this is not required: Some ViewResolvers will always attempt
to build View objects with the given name, unable to return
(rather throwing an exception when View creation failed).
viewName- name of the view to resolve
locale- Locale in which to resolve the view. ViewResolvers that support internationalization should respect this.
nullif not found (optional, to allow for ViewResolver chaining)