In order to keep up with the times ;) we should modify the way we are configuring Spring in most of our Spring-enabled example applications and use JavaConfig instead of XML. As a consequence, this will also mean modifying some parts of our documentation (tutorials, articles) which include snippets of Spring configuration code, currently in XML.
The list of modifications to be done are:
The STSM app (thymeleaf/thymeleafexamples-stsm#2), and the "Thymeleaf + Spring" tutorial.
The extrathyme app (thymeleaf/thymeleafexamples-extrathyme#1), and the "Extending Thymeleaf" tutorial.
The springsecurity app (thymeleaf/thymeleafexamples-springsecurity#2), and the corresponding "Thymeleaf + Spring Security integration basics" article.
The springmail app (thymeleaf/thymeleafexamples-springmail#4), and the corresponding "Rich HTML email in Spring with Thymeleaf" article.
The thvsjsp app (thymeleaf/thymeleafexamples-thvsjsp#1), and the corresponding "Spring MVC view layer: Thymeleaf vs. JSP" article.
The sayhello app (thymeleaf/thymeleafexamples-sayhello#1), and the corresponding "Say Hello! Extending Thymeleaf in 5 minutes" and "Say Hello Again! Extending Thymeleaf even more in another 5 minutes" articles.
Note that, for the "Thymeleaf + Spring" tutorial (and only for that one), it would be nice to keep a couple of code samples --only the most relevant ones-- in the docs in both versions, XML and JavaConfig, so that we cover both possibilities. For example, this could apply to the samples explaining how the ViewResolver and all related beans like TemplateEngine, TemplateResolver, etc. are registered, but not further than their first appearance, and never for more advanced concepts like registering the ConversionService and such.
Also note that we can exclude the petclinic application from this refactoring, given it is much more complex and after all it basically mirrors a standard Spring sample application, which was using XML at least when we forked it.
In order to keep up with the times ;) we should modify the way we are configuring Spring in most of our Spring-enabled example applications and use JavaConfig instead of XML. As a consequence, this will also mean modifying some parts of our documentation (tutorials, articles) which include snippets of Spring configuration code, currently in XML.
The list of modifications to be done are:
Note that, for the "Thymeleaf + Spring" tutorial (and only for that one), it would be nice to keep a couple of code samples --only the most relevant ones-- in the docs in both versions, XML and JavaConfig, so that we cover both possibilities. For example, this could apply to the samples explaining how the
ViewResolverand all related beans likeTemplateEngine,TemplateResolver, etc. are registered, but not further than their first appearance, and never for more advanced concepts like registering theConversionServiceand such.Also note that we can exclude the petclinic application from this refactoring, given it is much more complex and after all it basically mirrors a standard Spring sample application, which was using XML at least when we forked it.