You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Spring will include compilation of expressions based on MapAccessor in version 4.2.4 (see https://jira.spring.io/browse/SPR-13638 ), so it seems like a good idea to add some way to enable the SpelCompiler for SpringEL expressions if Spring version is >= 4.2. First preliminary results show a 35% performance increase in some thymeleaf benchmarks thanks to the use of this expression compiler.
The SpelCompiler appeared in 4.1, but it's not until 4.2 that the same expressions can be used safely for different types of data without exceptions being issued, so it is 4.2 the version of Spring we should be aiming for. Also, it might be sensible to keep the compiler disabled by default for now (though this will depend on some additional testing), and have its activation depend on some kind of configuration property in SpringStandardDialect.
The text was updated successfully, but these errors were encountered:
Also note that, in order for most Thymeleaf expressions to be able to properly benefit from the SpEL compiler, version 4.2.4 (at least) of the Spring Framework is required.
Spring will include compilation of expressions based on
MapAccessor
in version 4.2.4 (see https://jira.spring.io/browse/SPR-13638 ), so it seems like a good idea to add some way to enable the SpelCompiler for SpringEL expressions if Spring version is >= 4.2. First preliminary results show a 35% performance increase in some thymeleaf benchmarks thanks to the use of this expression compiler.See http://docs.spring.io/spring/docs/current/spring-framework-reference/html/expressions.html#expressions-spel-compilation
The SpelCompiler appeared in 4.1, but it's not until 4.2 that the same expressions can be used safely for different types of data without exceptions being issued, so it is 4.2 the version of Spring we should be aiming for. Also, it might be sensible to keep the compiler disabled by default for now (though this will depend on some additional testing), and have its activation depend on some kind of configuration property in
SpringStandardDialect
.The text was updated successfully, but these errors were encountered: