New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initialization of Themes object raises an NPE in offline execution #26
Comments
Fixed in 2.0.18-SNAPSHOT. See associated test: https://github.com/thymeleaf/thymeleaf-tests/blob/20130616/src/test/java/org/thymeleaf/tests/offline/OfflineTest.java |
Reopening this. Due to a very weird issue during the packaging of 2.0.18 distribution jars, this is solved both in 2.0.18-SNAPSHOT and 2.0.19-SNAPSHOT, but not in 2.0.18 release. Tests went OK because they execute on the snapshot versions (both last 2.0.18-SNAPSHOT and first 2.0.19-SNAPSHOT contain the fix). Will have to release 2.0.19 really soon in order to solve this (and the javascript inlining stuff at the core) definitively :-( |
Nah, false alarm. 2.0.18 works just fine and this fix is correctly included. Closing again. Sorry! |
…g#26. Renaming of an old method.
When using the Spring-enabled template engine (
SpringTemplateEngine
class) in an offline environment, a NullPointerException is raised by theThemes
object constructor.See http://forum.thymeleaf.org/Help-needed-with-TemplateProcessingException-Exception-evaluating-SpringEL-expression-td4026209.html
This happens because, in offline execution, no Spring
RequestContext
object is available.Should be fixable by first checking whether we are in an online (
IWebContext
) or offline (IContext
) scenario before creating theThemes
instance.The text was updated successfully, but these errors were encountered: