The other two ( order and viewNames) are both optional, and have the same meaning as in the JSP ViewResolver we saw before. The templateEngine parameter is, of course, the SpringTemplateEngine object we defined in the previous chapter. These two classes will be in charge of processing Thymeleaf templates as a result of the execution of controllers.Д¬onfiguration of the Thymeleaf View Resolver is very similar to that of JSPвЂ™s: Thymeleaf offers implementations for the two interfaces mentioned above: viewNames allows the definition (with wildcards) of the view names that will be resolved by this ViewResolver.ДЈ.2 Views and View Resolvers in Thymeleaf.order establishes the order in which the ViewResolver will be queried in the chain.prefix and suffix work in a similar way to the attributes of the same names in ThymeleafвЂ™s TemplateResolver objects.This is needed for a JSP resolver, but it will not be needed at all when weвЂ™re working with Thymeleaf. viewClass establishes the class of the View instances.If a ViewResolver is asked a view that has no corresponding bean -which is the common case-, a new View object is created ad hoc and returned.ДЄ typical configuration for a JSP+JSTL ViewResolver in a Spring MVC application looks like this: ДЄ quick look at its properties is enough to know about how itвЂ™s configured: Note that not all pages in our applications have to be defined as Views, but only those which behaviour we wish to be non-standard or configured in a specific way (for example, by wiring some special beans to it. Typically, controllers ask ViewResolvers to forward to a view with a specific name (a String returned by the controller method), and then all the view resolvers in the application execute in ordered chain until one of them is able to resolve that view, in which case a View object is returned and control is passed to it for the renderization of HTML. ViewResolvers are the objects in charge of obtaining View objects for a specific operation and locale. Views are in charge of rendering the actual HTML interface, usually by the execution of some template engine like JSP (or Thymeleaf). Views model pages in our applications and allow us to modify and predefine their behaviour by defining them as beans. There are two interfaces in Spring MVC that conform the core of its templating system: 3 Views and View Resolvers 3.1 Views and View Resolvers in Spring MVC Instead, you should instance a new template engine class that performs all the required configuration steps:. Note that you shouldnвЂ™t use this dialect directly in a normal TemplateEngine object as a part of its configuration. New DTDs for validation, including these new attributes, as well as new corresponding DOCTYPE translation rules.An expression object and method, #mvc.uri(.), which is equivalent to the spring:mvcUrl(.) JSP custom function (only in Spring 4.1+).An expression object and method, #de(.), which is equivalent to the spring:theme JSP custom tag.Access any beans in your application context using SpringELвЂ™s syntax: New attributes for form processing: th:field, th:errors and th:errorclass, besides a new implementation of th:object that allows it to be used for form command selection.

jar files ( thymeleaf-spring3- expressions will be evaluated by SpringвЂ™s Expression Language engine. These libraries are packaged in separate. Note that Thymeleaf has integrations for both versions 3.x and 4.x of the Spring Framework, provided by two separate libraries called thymeleaf-spring3 and thymeleaf-spring4. This tutorial explains how Thymeleaf can be integrated with the Spring Framework, especially (but not only) Spring MVC. 12.1 Integration with RequestDataValueProcessor.11.2 Specifying fragments in controller return values.11.1 Specifying fragments in view beans.Simplifying error-based CSS styling: th:errorclass.3.2 Views and View Resolvers in Thymeleaf.3.1 Views and View Resolvers in Spring MVC.

Spring 4 new features