Open RaimondKempees opened 8 years ago
It looks interesting. If you cannot loop back to Spring MVC from a Thymeleaf view, you need to render the component presentations from the page controller, and hand the entire set of rendered CPs to the page view. Would that work with Thymeleaf?
Something like that. I'm investigating it at the moment. :)
Love to see this in the enhancement list! We are using this in our DD4T1.3 implementation and intend to use it as we move to DD4T2. Hooking up a Thymeleaf view resolver is trivial, but it doesn't support include or forward operations like JSP, so once you've delegated to the view you cannot loop back into the Spring web flow. You can leverage utility classes that are called in Thymeleaf to do any additional logic on your model (or do it in Thymeleaf itself, but I prefer to keep Java code in Java).
I'm curious what you have in mind for this enhancement. Seems to me that DD4T is flexible enough to allow for a Thymeleaf view implementation. Are you thinking of changes in the example site or in the spring-mvc-support or something else?