One another feature of the new fragment expression is so called no-operation token that allows the default markup of the fragment to be used in case this is needed: įragment Expression enables the customization of fragments in ways that until now were only possible using the 3rd party Layout Dialect. It will pass an empty value that will be ignored in the header fragment: The home/homeNotSignedIn.html template is rendered when the anonymous user enters the home page of our application.Ĭlass HomeController index(Principal principal). This allows the grouping of fragments into one or several pages. Thymeleaf can include parts of other pages as fragments (whereas JSP only includes complete pages) using th:insert (it will simply insert the specified fragment as the body of its host tag) or th:replace (will actually substitute the host tag by the fragment’s). Basic inclusion with th:insert and th:replace Thymeleaf Standard Layout System offers page fragment inclusion that is similar to JSP includes, with some important improvements over them. Example ApplicationĪll the samples and code fragments presented in this article are available on GitHub at Thymeleaf Standard Layout System The main advantages of this solution are the reuse of atomic portions of the view and modular design, whereas the main disadvantage is that much more configuration is needed in order to use them, so the complexity of the views is bigger than with Include Style Layouts which are more “natural” to use.
In Thymeleaf this can be done using Thymeleaf Layout Dialect. Each component of the template may be included dynamically based on the inclusion and substitution of template fragments. In hierarchical style, the templates are usually created with a parent-child relation, from the more general part (layout) to the most specific ones (subviews e.g. page content). The main disadvantage of this solution, though, is that some code duplication is introduced so modifying the layout of a large number of views in big applications can become a bit cumbersome. The include-style layouts are pretty simple to understand and implement and in fact they offer flexibility in developing views, which is their biggest advantage. In Thymeleaf this can be done using Thymeleaf Standard Layout System: In this style pages are built by embedding common page component code directly within each view to generate the final result.
Both styles can be easily utilized with Thymeleaf without losing its biggest value: natural templating. There are two main styles of organizing layouts in projects: include style and hierarchical style. These page components can be used by the same or different layouts. Usually websites share common page components like the header, footer, menu and possibly many more.
0 kommentar(er)
