On Nov 19, 2007 11:39 AM, Jim Cushing <[EMAIL PROTECTED]> wrote:
> I hope that Struts 2 continues to strongly support Freemarker. In
> fact, I wish they promoted it as the preferred choice.

FreeMarker is cool, but I'm still a die-hard Velocity fan :)

Here's the thing: If we started using FreeMarker or Velocity as our
primary examples, this move would quickly turn into FUD like about the
group abandoning JSP. And, realistically, the people who need the most
help from the examples are newbies being forced to use JSPs.

Though, I would agree that our FreeMarker and Velocity documentation
could go into greater detail of why these systems are technically
superior to JSPs, and we could use many more ftl/vt cookbook articles.
(Feel free to contribute!)


On Nov 19, 2007 12:55 PM, Brian Pontarelli <[EMAIL PROTECTED]> wrote:
> [JAR-ability] is one of the main reasons why FreeMarker and Velocity were 
> added
> as engines to WebWork and Struts.

Back in the day, *all* of the other MVC frameworks focussed on
Velocity. I'd wager that, more than anything else, the JSP taglib is
the reason why people are using Struts today, rather than Barracuda or
Maverick or Turbine, or several others that existed before Struts 1
shipped.

At first, people touted that templates were safer and better suited
for MVC since there were no scriptlets (good point!). Later, people
added the argument that we could put templates in JARS (better
point!). Being able to load JSPs from the classpath would definitely
be the single biggest functional upgrade to the technology.

-Ted.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to