Broken execution of processors

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Broken execution of processors

Thibault Duchateau
This post was updated on .
Hi,

I'm a bit puzzled by an issue I'm trying to fix.

In the following snippet of code...

<div dt:conf="myTableId">
   <div dt:confType="extrahtml">
      <a th:each="bean : ${collection}" th:text="${bean.property}">...</a>
   </div>
</div>

... the issue is that the "a" tag, with the "th:each" attribute attached to it, doesn't get processed at all.

A custom processor is applied on the "div" element with the "dt:conf" attribute.
Another processor on the "div" element with the "dt:confType" attribute.

I've made some tests, e.g. by removing the several securities about the attributes usage and tried to remove both "dt:conf" and "dt:confType" attributes. In this case, both "th:each" and "th:text" get processed, but I don't understand why.

In a nutshell, I don't understand why my custom processors break the processing of inner nodes.

Does anyone have any idea?

Thymeleaf: 2.1.3.RELEASE
Template mode: HTML5

EDIT: I made more tests.

#1: Removing dt:conf="myTableId" in the first div
<div>
   <div dt:confType="extrahtml">
      <a th:each="bean : ${collection}" th:text="${bean.property}">...</a>
   </div>
</div>
=> it works (I mean, th:each and th:text are processed)

#2: Removing dt:confType="extrahtml" in the nested div
<div dt:conf="myTableId">
   <div>
      <a th:each="bean : ${collection}" th:text="${bean.property}">...</a>
   </div>
</div>
=> it works

#3: Removing both dt:conf="myTableId" (first div) and dt:confType="extrahtml" (nested div)  
<div>
   <div>
      <a th:each="bean : ${collection}" th:text="${bean.property}">...</a>
   </div>
</div>
=> it works

#4: Removing nothing
<div dt:conf="myTableId">
   <div dt:confType="extrahtml">
      <a th:each="bean : ${collection}" th:text="${bean.property}">...</a>
   </div>
</div>
=> it doesn't work

Regards,
Thibault.
Reply | Threaded
Open this post in threaded view
|

Re: Broken execution of processors

Thibault Duchateau
Sorry guys, the problem was actually located between the chair and the keyboard...