Originally posted by Karthik Guru:
My first impressions about VTL ( velocity template language) is that it is way far easier than XSL.
XSL works on top of the xml that you supply while Velocity reads data out the java objects you populate in the Velocity context.
that content generation using velocity would be faster than corresponding xsl transform?..just a guess)
As an earlier poster described, I once considered transforming Java objects into XML and then transforming the XML into HTML or whatever for rendering. At first this sounds like a great idea since you can swap out one stylesheet for another and get a completely new look. However, the performance of such a solution is, in general, diabolical when compared Velocity or JSP. Unless your data is already in XML format, by that I mean it is stored in XML or arrives to you in XML, then I would recommend using Java objects to represent the model data and Velocity templates to render the view.
Originally posted by Rob Harrop:
Certainly, transforming data into XML just so you can transform it into another form is generally wasted effort and offers no real benefit for your application.
Stick with a simple object model that you render using Velocity (or JSP) and you will avoid stunting your application with unnecessary complexity.
Yes, I suspect this would be a hard sell. The only reason I would entertain it is that we are already reworking the logic in the presentation layer and then reskinning the site (certainly adding new features requiring more web tier changes).
Originally posted by Ali Pope:
However keep in mind that migrating from XSL to any other solution will take a very long time, big efforts and will represent a real shift in your dev environment.
Think of how stupid the average person is. And how half of them are stupider than that. But who reads this tiny ad?
the value of filler advertising in 2020https://coderanch.com/t/730886/filler-advertising