|
From: Rob H. <ro...@in...> - 2006-04-28 10:39:41
|
All, As part of the RC1 release I will be revisiting the way XSLT views are constructed in Spring MVC. This is work I plan to carry out alongside (http://opensource.atlassian.com/projects/spring/browse/ SPR-1249). I plan to introduce an XsltView class that *does not* require subclassing and a corresponding XsltViewResolver. The basic idea is to have a view that functions in a similar manner to the JasperReports view. The view name will be translated into an XSLT template URI by the ViewResolver and an XsltView instance for that XSLT template will be created. Then the view will attempt to locate the source in the Model using a simple resolution algorithm. I propose that this algorithm will search for: 1. DOM Documents 2. Node objects 2. Source objects 3. Strings? 4. Readers? It will convert this into Source implementations as appropriate and expose them to the XSLT processor. It will be possible to configure the exact name of the Model parameter to look at for this source object, to provide deterministic semantics in more complex use cases. Any other ideas/requests - let me know. Rob |