Very easy to learn template language - even casual users can learn it, so it's not just for programmers.
Velocity 1.5 is slow
This is Stan from India..
I have recently upgraded velocity 1.4 to velocity 1.5
And all the related jar files are updated..
I face a problem that.. the performance is down when updated from 1.4 to 1.5 in the development environment.. I mean that I have configured my project in JbossIDE 1.6
When I debug from there.. the performance is slow compared to velocity 1.4.. Why ?
But the performance is equal when I run the jboss in the run mode.. By running the run.bat file..
Need your reply soon..
Re: Ownership change?
Thanks. That'll do nicely! :)
> I just added you as an Owner. =)
> % Hey Jon, would you be willing to cede
> % ownership of the Velocity project's
> % presence here at freshmeat so we can
> % update it?
Re: Ownership change?
I just added you as an Owner. =)
> Hey Jon, would you be willing to cede
> ownership of the Velocity project's
> presence here at freshmeat so we can
> update it?
Hey Jon, would you be willing to cede ownership of the Velocity project's presence here at freshmeat so we can update it?
It's worth nothing that Velocity is a clone of WebMacro, due to incompatibilities between the Apache and GNU licenses.
Re: why not xslt instead
This isn't really the correct forum for this discussion (the
velocity-user mailing list is), but here are some
thoughts that I have on your question:
In this usecase, I can think of one major advantage of
Velocity over XSLT. In XSLT, the input format MUST be in
a format that can be parsed by a XML parser (ie: XML,
XHTML, etc). With Velocity, there is no need for the
input to be parsed by an XML parser (it is parsed by
the Velocity parser which is based on JavaCC and can
parse both text AND binary files!). For example, one
can use Velocity to output dynamically generated Java
.java code (the Jakarta-Turbine-Torque project does
this). Try doing that in XSLT.
Another advantage of Velocity over XSLT is speed.
Velocity is significantly faster than XSLT.
Velocity is small and compact (304k jar + 70k for logkit
logging jar) and does not require a lot of memory. XSLT
requires both the xerces parser (a 1.7+meg .jar file) as
well as the xalan engine (700k+).
Lastly, Velocity is *easy*. XSLT takes a degree in
software engineering to figure out :-). Velocity can be
learned in a matter of minutes by anyone. The reason
why there is so much reference material for XSLT is
because it is so overly complex and difficult to learn,
people need it. If you review the Velocity website, you
will see that it is well documented with both an up-to-
date userguide and developers guide.
I hope that answers your questions.
> I do not understand the advantage of
> velocity over xslt.
> Why should I learn yet another
> programming language
> (vtl) rather than using xsl which has
> more reference
> material and seems to be more
why not xslt instead
I do not understand the advantage of velocity over xslt.
Why should I learn yet another programming language
(vtl) rather than using xsl which has more reference
material and seems to be more popular?
An open, cross-platform journaling program.
A scientific plotting package.