Administrator
|
Thymeleaf 3.0.8 (3.0.8.RELEASE) has been just published. This is a maintenance release with some bugfixing and feature changes. It should work as a drop-in replacement for 3.0.x versions. Have a look at our Download Page to learn how to obtain it. This is also the first GA version of the thymeleaf-spring5 integration module, that now depends on the very recent Spring Framework 5.0.0.RELEASE. THYMELEAF 3.0.8 CHANGE LOGChanges to the Thymeleaf CORE:
Changes to the Thymeleaf SPRING integration packages:
If you are interested, you can have a look at the list of issues on GitHub:
And of course we invite you to visit the project website at http://www.thymeleaf.org SPECIAL NOTES FOR THE Spring 5 WebFlux INTEGRATIONHow does Thymeleaf operate in a reactive-friendly way for Spring 5 WebFlux? Like previous versions, this new version of the Spring 5 integration module includes updated support for the new Spring 5 WebFlux reactive web framework. When used with WebFlux, Thymeleaf can operate in one of three reactive-friendly modes:
Read more about these reactive-friendly operation modes at the thymeleaf-spring5 JavaDocs. Also, note that there are three sandbox applications prepared to serve as examples of the general thymeleaf-spring5 integration with Spring 5 WebFlux:
Regards, |
Great news!!
Are there any changes in th:errors? Before upgrading from 3.0.7 th:errors="*{fieldname}" shows the error of the specified field. With 3.0.8 no error-content is rendered. Using th:error="*{fieldname}" instead works. API change or bug? Many thanks and best regards. |
Administrator
|
Hello dasa,
There have been no changes to th:errors, and actually there is no such "th:error" attribute processor neither in 3.0.7 nor in 3.0.8. Could you please re-check this scenario and, if you confirm your issue, please add a GitHub ticket giving the most detail possible? (version of Spring, etc.) Thanks, Daniel |
Hello Daniel,
thank your for your fast check and reply. Strage, i re-checked the scenario - th:errors does not work for a single field error, only for global errors - th:error works for a field error ... somewhat magic ... My setup: - Tomcat 8.5.20 - Spring 5.0.0.Release - Spring Security 4.2.3.RELEASE (also testet with 5.0.0.M3) - Thymeleaf 3.0.8.RELEASE - thymeleaf-spring5 3.0.8.RELEASE - thymeleaf-layout-dialect 2.2.2 - thymeleaf-extras-springsecurity4 3.0.2.RELEASE (cuurently there is no 5 version available) Because we are moving from Spring 4 to Spring 5 upgrade to Thymeleaf 3.0.8 is needed. I will try a setup with Spring 4 and Tyhmeleaf 3.0.8 and 3.0.7 to check if it is a Spring 4/5 or an Thymleaf issue. Best regards |
Hello Daniel,
after debugging a while, i found that this has nothing to do with Thymeleaf, it is an changed behaviour of Spring 5 Message resolving mechanism that returns an empty string (not a null value) by asking the ParentMessageSource if the actual MessageResolver does not find a message for a given code. Additionally: th:error does not exists (your right!) and simply does nothing but leafs the default text in the html-template (which looks like the th:error has done his job ...) Sorry for my misunderstanding ! Best Regards. |
Free forum by Nabble | Edit this page |