The Standard Dialect is the dialect this tutorial covers. Every attribute and syntax feature you will learn about in the
following pag es is defined by this dialect, even if that isn’t explicitly mentioned.
Of cours e, users may create their own dialects (even extending the Standard one) if they want to define their own
proces sing logic while taking advantag e of the library’s advanced features . A Template Engine can be configured
several dialects at a time.
The official thymeleaf-spring 3 and thymeleaf-spring 4 integ ration packag es both define a dialect called
the “Spring Standard Dialect”, mostly equivalent to the Standard Dialect but with small adaptations to
make better use of some features in Spring Framework (for example, by using Spring Expression
Lang uag e instead of Thymeleaf’s standard OGNL). So if you are a Spring MVC user you are not wasting
your time, as almost everything you learn here will be of use in your Spring applications.
The Thymeleaf Standard Dialect can proces s templates in any mode, but is es pecially suited for web-oriented
template modes (XHTML and HTML5 ones). Besides HTML5, it specifically supports and validates the following XHTML
specifications: XHTML 1.0 Transitional, XHTML 1.0 Strict, XHTML 1.0 Frameset, and XHTML 1.1.
Mos t of the proces sors of the Standard Dialect are attribute processors. This allows browsers to correctly display
XHTML/HTML5 template files even before being processed, because they will simply ig nore the additional attributes.
For example, while a JSP using tag libraries could include a frag ment of code not directly displayable by a browser like:
<form:inputText name="userName" value="${user.name}" />
…the Thymeleaf Standard Dialect would allow us to achieve the same functionality with:
<input type="text" name="userName" value="James Carrot" th:value="${user.name}" />
Which not only will be correctly dis played by browsers , but also allow us to (optionally) specify a value attribute in it
(“James Carrot”, in this case) that will be displayed when the prototype is statically opened in a browser, and that will
be substituted by the value res ulting from the evaluation of ${user.name} during Thymeleaf proces sing of the
template.
If needed, this will allow your desig ner and developer to work on the very same template file and reduce the effort
required to transform a static prototype into a working template file. The ability to do this is a feature usually called
Natural Templating.
1.4 Overall Architecture
Thymeleaf’s core is a DOM processing engine. Specifically, it us es its own high-performance DOM implementation —
not the standard DOM API— for building in-memory tree representations of your templates , on which it later operates
by traversing their nodes and executing proces sors on them that modify the DOM according to the current
configuration and the s et of data that is pas sed to the template for its representation —known as the context.
The use of a DOM template representation makes it very well suited for web applications because web documents are
very often represented as object trees (in fact DOM trees are the way browsers represent web pag es in memory).
Also, building on the idea that mos t web applications use only a few dozen templates, that these are not big files and
that they don’t normally change while the application is running , Thymeleaf’s usag e of an in-memory cache of parsed
template DOM trees allows it to be fast in production environments, because very little I/O is needed (if any) for most
template proces sing operations.
If you want more detail, later in this tutorial there is an entire chapter dedicated to caching and to the
way Thymeleaf optimizes memory and resource usag e for faster operation.
Nevertheless , there is a res triction: this architecture also requires the use of big g er amounts of memory space for
我的内容管理
收起
我的收益 登录查看自己的收益
我的积分
登录查看自己的积分
我的C币
登录后查看C币余额
我的收藏 
我的下载 
下载帮助 
评论1