Quoting Ray Cromwell ([EMAIL PROTECTED]):
> 2) Uses StreamTokenizer and hand coded parser, with parse
> rules implemented via a static parse() function on each directive.
Not any more, that used to be true.
> 1) Hardcoded directive array in Block.java should be moved to property file, or some
> other easy to configure or dynamic mechanism that doesn't require a recompile.
Directives are now loaded via the broker.
> 2) #parse and #include (IncludeDirective superclass) are inefficient,
> because they bypasses caching.
Not any more.
> While the Template method may cache the
> parsed template, it doesn't cache *included* content or templates,
> therefore #include causes the included file to be re-read everytime the
> evaluation phase occurs. Meanwhile, #parse causes re-reading, and
> re-parsing.
Again, not anymore.
My point in saying you had no idea what WM does is that your list of things
a template system does left out most of WM's functionality.
Justin
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
