It appears to me that the idea of transforming POJOs into JavaScript objects is taken from DWR. Even though in DWR the config is required it can be combined with Spring in one xml file. Integration is quite smooth and supports the idea of non-intrusive framework usage as remoted POJOs do not need to extend any classes.
Interesting in here is the client-side template-based view layer. But as was admitted the XSL transformation is heavy and in fact it is double transformation (JS->XML->HTML) behind the scenes. What would be really interesting is some kind of template engine written in JavaScript analogous to something like StringTemplate in server-side java. This engine would compile HTML-based templates (and probably keep them cached for better performance) and generate output with parameters being JavaScript model objects retrieved using remoted POJOs. |
java.net RSS Feeds
