Another choice would be a template system like WebMacro. These are add
ons to the servlet environment. You still write regular processing code
in the back end, in ordinary Java, but you create and use templates to
generate the HTML.
Unlike JSP the templates don't have any programming code in them, just
variables and directives for how the page should look.
http://webmacro.org
The htmlKona/ECS type systems are not appropriate mechanisms for
separating programming and HTML; however if you have a lot of automatically
generated objects they can be quite appropriate.
Whether a template or kona approach is best depends on what you're doing.
Justin
Quoting Mike Engelhart ([EMAIL PROTECTED]):
> I've always questioned this (htmlKona, etc) though for anything other than
> simple sites. I can't even imagine the overhead of creating hundreds of
> objects per request just to output HTML. At least in my instance the pages
> are pretty complex with lots of tables for formatting, etc.
>
> mike
>
> ----------
> >From: Uddipan Bagchi <[EMAIL PROTECTED]>
> >To: Mike Engelhart <[EMAIL PROTECTED]>
> >Cc: [EMAIL PROTECTED]
> >Subject: Re: JSP vs. Servlets?
> >Date: Fri, Oct 15, 1999, 12:04 AM
> >
>
> > There are html wrapper classes available (eg. htmlKona) that u can use to make
> it
> > more pleasant than the above. These do it in an object way, and it is easier
> to
> > keep track, debug, and, wonder of wonders, make changes to the presentation.
>
> ===========================================================================
> 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
===========================================================================
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
