- All Implemented Interfaces:
view-resolversMVC namespace element and registers
All registered resolvers are wrapped in a single (composite) ViewResolver with its order property set to 0 so that other external resolvers may be ordered before or after it.
When content negotiation is enabled the order property is set to highest priority instead with the ContentNegotiatingViewResolver encapsulating all other registered view resolver instances. That way the resolvers registered through the MVC namespace form a self-encapsulated resolver chain.
parseDescription copied from interface:
BeanDefinitionParserParse the specified
Elementand register the resulting
BeanDefinitionRegistryembedded in the supplied
Implementations must return the primary
BeanDefinitionthat results from the parse if they will ever be used in a nested fashion (for example as an inner tag in a
<property/>tag). Implementations may return
nullif they will not be used in a nested fashion.