JSP style on demand background compilation. about jte HOT 5 CLOSED

from jte.

@hurelhuyag thanks for the heads up!

@tstsogoo is right, jte already supports hot reload during development, when using a DirectoryCodeResolver.

var codeResolver = new DirectoryCodeResolver(Path.of("jte")); // This is the directory where your .jte files are located.
var templateEngine = TemplateEngine.create(codeResolver, ContentType.Html);

Maybe you used a ResourceCodeResolver? That one does not support hot reload.

from jte.

If hot reload is like JSP does why it is not recommended in production environment? I'm expecting production grade hot reloading feature.

from jte.

Obviously, you can use jte in production the same way as during development.

There are few reasons I would not recommend it:

• Performance: Hot reloading does an additional check on the file system, which is almost always unneccessary on a production system
• Security: Hot reloading on production requires a JDK to recompile templates. If you are able to change templates on production, you really have to secure this. If something goes wrong, you immediately have a remote code execution vulnerability

That being said, since version 1.5.0 there is a way for hot reload on production, without paying the performance penalty. This unit test illustrates how you'd do that. However, the security concern is still valid, so please be careful.

from jte.

Thanks. I got it.

from jte.