For the moment, the TemplateParser implementations are too linked with our default strategy. As it is, the TemplateBuilder class and TemplateParserBuilder classes does not allow easily (I guess they even forbid it) to change the strategy and define your own adapters. The problem is the same for Thymeleaf or FreeMarker : we don't have a clear separation between a #useDefaults() method and a ad-hoc configuration by the developper.
Ex for FreeMarker :
@see
FreeMarkerTemplateParserBuilder#build()
TemplateBuilder#build()
FreeMarkerFirstSupportingTemplateLoader
usages of FirstSupportingResourceResolver and FirstSupportingResolverAdapter
For the moment, the TemplateParser implementations are too linked with our default strategy. As it is, the TemplateBuilder class and TemplateParserBuilder classes does not allow easily (I guess they even forbid it) to change the strategy and define your own adapters. The problem is the same for Thymeleaf or FreeMarker : we don't have a clear separation between a #useDefaults() method and a ad-hoc configuration by the developper.
Ex for FreeMarker : @see