>The difference is that http://www.bgeer.com/dexios doesn't "compile" the
>templates into servlets. The templates have macro variables, loops, and
>conditionals --that are evaluated by the servlet, and then macro variable
>substitution is performed and the template is output. (see
>http://www.bgeer.com/dexios/template/docs/tutorial.html#example )
That seems to be the most natural way to think about, and the dexios
package seems more natural and intuitive to me. But just look at the
popularity of ASP -- "clean" doesn't always cut it.
We're using JSP here for the single reason that we expect it to be an
industry standard. It will be much easier (we hope) to find people who can
modify HTML with JSP markup than with any of the hundreds of existing
template systems out there.
>I guess I am getting hung up on this idea of having to write script in a
>template.... although I must admit I need to investigate the bean aspect
of JSP
>more....
I'd definitely suggest it. Our goal here is to have the absolute minimum
amount of scripting in the templates. The USEBEAN tags provide a way to
have the dynamic text producing elements as standard Javabeans which are
completely separated from the templates, which IMO is really the best
possible solution.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
