Closed makigumo closed 2 years ago
This is by design. Due to both security and web compatibility reasons, these objects are not considered expression utility objects anymore. If these objects are needed, they will need to be added to the model at the controller, though note that calling arbitrary methods on javax.*
and jakarta.*
objects has been forbidden too. The release notes for 3.1.0.M1
(to be published) wil explain all this.
Thank you for the given insight.
Hello!
Please find attached a project (demo.zip) to demonstrate the issue. After running it, please navigate to http://localhost:8080/
This is the source template:
This is the result with spring boot 3.0.0-M1.
This is the expected result, returned after changing to spring boot 2.6.3 in
build.gradle
.demo.zip