Provide support for Servlet 5.0
See original GitHub issueThymeleaf depends on the Servlet API 2.5 at the moment. Servlet 5.0, which will be part of the Jakarta EE 9 release, migrated the javax.*
to the new jakarta.*
package namespace. It would be great to see a Thymeleaf version that supports this new package namespace.
Are there any plans for this at the moment?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:10
- Comments:19 (6 by maintainers)
Top Results From Across the Web
Jakarta Servlet Specification
The Jakarta Servlet API v.5.0 is a required API of the Jakarta EE Platform, 9. Servlet containers and servlets deployed into them must...
Read more >Jakarta Servlet 5.0 - IBM
This feature enables support for HTTP Servlets written to the Jakarta Servlet 5.0 specification. You can package servlets in Jakarta EE specified WAR...
Read more >Jakarta Servlet 5.0 :: Open Liberty Docs
This feature enables support for HTTP Servlets written to the Jakarta Servlet 5.0 specification. You can package servlets in Jakarta EE specified WAR...
Read more >upgrade servlet 4.0.1 to servlet 5.0 - java - Stack Overflow
I am upgrading servlet 4.0.1 to servlet 5.0. No, that is not actually an « upgrade ». There is no significant change in...
Read more >Servlet (Servlet 5.0 API Documentation - Apache Tomcat
Called by the servlet container to indicate to a servlet that the servlet is being placed into service. · Called by the servlet...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The first milestone of Thymeleaf 3.1.0 has just been released.
The following artifacts have been published to Maven Central:
org.thymeleaf
:thymeleaf
:3.1.0.M1
org.thymeleaf
:thymeleaf-spring5
:3.1.0.M1
org.thymeleaf
:thymeleaf-spring6
:3.1.0.M1
org.thymeleaf.extras
:thymeleaf-extras-springsecurity5
:3.1.0.M1
org.thymeleaf.extras
:thymeleaf-extras-springsecurity6
:3.1.0.M1
org.thymeleaf
:thymeleaf-testing
:3.1.0.M1
org.thymeleaf
:thymeleaf-testing-spring5
:3.1.0.M1
org.thymeleaf
:thymeleaf-testing-spring6
:3.1.0.M1
In Spring-based applications, Spring structures (e.g.
ThymeleafView
) should hide most/all of the complexity of the switch to the new version. Non-Spring-based applications will need a couple of adaptations in order to work with the new abstraction structures that allow Thymeleaf to work in several web environments (javax
Servlets,jakarta
Servlets, Spring WebFlux). Release notes will be published later today explaining the relevant changes.Example applications (
thymeleafexamples-*
) are also being updated to the new version and new structures by creating new branches for them. e.g.3.1-master
,3.1-master-jakarta
,3.1-master-spring6
…Let me know if there is anything I can do to help with getting this done. Thymeleaf is the most popular third party view engine for Jakarta MVC. So it would be great if we could ship it as part of the upcoming 2.0 release.