On 2/4/06, Malcolm Edgar <[EMAIL PROTECTED]> wrote: > Hi Will, > > Yes the error handling issue is pretty well nailed now in 1.5. > > 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.
i dunno. the defaults seem to work pretty well to me. for the core, the current directory is the default template location and there's a reasonable (and recently much improved) log facility lookup heirarchy. for the VelocityViewServlet, the webapp root is the default template location. we have defaults. what defaults are the problem? > On a completely unrelated issue, I have been working with JSTL for the > last month or so. I had the impression that JSP had finally caught up > to Velocity with JSTL and EL. Well I was wrong, Velocity is still > head and sholders easier to use than JSTL. i feel your pain. i'm working on a JSTL/EL project right now and missing Velocity greatly. > regards Malcolm Edgar > > > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
