Yes the error handling issue is pretty well nailed now in 1.5.
Well, it did not seem as smooth as FreeMarker ;)
The issue of configuration is valid in that FM is much easier to
setup, principally because they default alot of configuration.
Possibly Vel could have some default setups, to help people get jump
started.
My point about default settings were *one* part of it. The default settings
is nice in FreeMarker, but that is actually not the import part. The
important
part is that I can use Java to configure it with; no need for non-typed
properties
settings which is unsafe AND does not allow me to refer to the configured
objects.
e.g. I have good usages of being able to actual reuse the exact same
TemplateLoaders
(or ResourceLoader as they are called in velocity) as the engine uses
directly in code.
just to let you know ;)
/max
On 2/5/06, Will Glass-Husain <[EMAIL PROTECTED]> wrote:
Hi,
Just wanted to highlight this article for members of the Velocity dev
community
http://blog.hibernate.org/cgi-bin/blosxom.cgi/2006/02/03#a_story_about_freemarker_and_velocity
This article describes why the author of the Hibernate Tools is moving
from Velocity to FreeMarker. Makes some good points about error
handling and application integration. Some of the concerns will be
alleviated with 1.5 but it's interesting to ponder his various points.
Cheers,
Will
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
[EMAIL PROTECTED]
http://hibernate.org
JBoss Inc
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
