The one thing that may prevent FreeMarker from being "drop-in" replacement for the WebWork JSP is the expression language supported by the WebWork taglibs. It also affects JSTL integration and Velocity integration. It concerns the hierarchical nature of the ValueStack. Most of these third-party view technologies don't understand the concept of '../name'. We use WebWork/Velocity on a huge project and have never had any need for this syntax, but some WebWork developers (I guess) use the hierarchical ValueStack quite often.

Since you "own" the FreeMarker syntax and can modify it, perhaps you may want to include such constructs.

On Tuesday, January 28, 2003, at 01:59 PM, Attila Szegedi wrote:

Actually if I understand it right, the integration is quite trivial. We have
a Model2-compliant view servlet bundled into the core distribution. It lets
templates access request, session, and servlet context attributes. It also
lets templates use any JSP taglib present in the webapp. Therefore it is
pretty much a drop-in replacement for JSP as far as WebWork is concerned. Is
there anything else codewise that should be done for integration? (My
feeling is that there isn't, but please correct me if there are some
gotchas).

-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork

Reply via email to