I'd recommend not using Cheetah templates as servlets -- it's better to have the template separate, and have the servlet call the template.
Would you please elaborate on that? We have done a couple of (large) projects using cheetahs "inheritance approach" without running into problems.
To me it just seems easier to think about and handle. E.g., often I have a servlet with several distinct templates. Or, less often, a template that several servlets use (e.g., an error message template). And the inheritance structure for templates doesn't necessarily relate to the inheritance structure of servlets.
It's not that one way is "right", it's just in my experience that it's ended up easier to keep templates separate.
-- Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Webware-discuss mailing list Webware-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/webware-discuss
