I finally broke down and looked at some of the Turbine code, because I wanted to know what people were talking about.
I did a CVS checkout of the head, jakarta-turbine-2, which is where all the commits seem to be going.
I then did a grep over the sources looking for the various points at which classes in the org.apache.velocity.* hierarchy are referenced.
I found 21 (!) different source files which reference Velocity classes. Now, there was again a reaction of irritation with this. Henning and a couple of other people had proposed (with a certain aggressive subtext) that there was some onus on *me* to submit a patch if I "wanted" the FM support back.
IMO, most of what is needed is to abstract the org.apache.velocity.context.Context class as a generic Template Context for the pull service and to substitute most "VelocityXXX" class names for "TemplateXXX"
Look for instance to the VelocityDirectLayout. It only uses the Context, and the main Velocity class to get it.
If the FM context for bean like object has a similar interface, it does not look like a daunting task.
[EMAIL PROTECTED] jakarta-turbine-2]$ egrep -Rl "org.apache.velocity.[^c]" src/java/
src/java/org/apache/turbine/services/pull/TurbinePullService.java
src/java/org/apache/turbine/services/velocity/TurbineVelocityService.java
Now, this work will be much better done if someone who knows the needs or specific template engines helps in the abstraction process of the context.
Just my 2 (Euro) cents.
(...)
Regards -- Santiago Gala High Sierra Technology, S.L. (http://hisitech.com) http://memojo.com?page=SantiagoGalaBlog
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
