on 10/5/2000 1:48 PM, "Gary Mangum" <[EMAIL PROTECTED]> wrote:
> 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.
>
> Thanks for your help.
> Gary
Sigh, because XML and XSL isn't the solution to everything. Just because
something is "standardized" doesn't mean that there is a need for other
things.
For example, Velocity can be used to send dynamic email easily, dynamically
create Java code (see Turbine's torque/newtorque stuff), dynamically create
XML files, and many many many other things.
As for the Context object, that is just a standard mechanism for
transporting information through the MVC layer.
-jon
--
http://scarab.tigris.org/ | http://noodle.tigris.org/
http://java.apache.org/ | http://java.apache.org/turbine/
http://www.working-dogs.com/ | http://jakarta.apache.org/velocity/
http://www.collab.net/ | http://www.sourcexchange.com/
