> I'm just learning about velocity, so I am trying to compare the velocity
> project with research that I have done into using XML and XSLT. I've also
> looked into the possibility of using Cocoon, another apache project, but
am
> not sure that it offers me what I need.
>
> Why is the velocity project setting up it's own parser and template
> language, instead of using the existing parser and template language found
> in XML and XSL??? It seems like what you are building is almost an exact
> match to what is already existant in XML and XSL, and they seem like the
> better choice since they are standardized. Your Context object matches
> information that would be incuded in XML, and your Template file matches
> functionality existant in XSL.
>
I love XML/XSL but it is *not* what Velocity does. For example - how would
you enter stuff that you extracted from a database to your page with XSL?
In our company we actually use Velocity and XSL stylesheets in combination!
We use Velocity template to create XML files from templates which is then
transformed with a XSLT to get the right presentation. Basically Velocity
adds dynamic content like database stuff (amongst others) and XSL does the
presentation.
2 Very different tools for 2 very different problem sets.
~ Leon
