Just an experienced perspective in the JSP vs. templates debate: I wrote a Servlet-based application a couple of years ago that used a template mechanism to separate the presentation from the data. It was a nice, flexible, powerful, reasonably fast, simple template language that was compatible with many WYSIWYG HTML editors. You could also change the HTML presentation without even restarting the server. (I did not even consider using JSPs because they simply weren't available at the time.) There ended up being two major problems with this when we actually went to release the application: 1) Noone wanted to learn the template language 2) We had to provide support for the template language JSPs are popular, they are widely-understood, there are nice tools to develop them, and other people can answer questions on them. I also do not feel that we are imposing on anyone by asking them to learn the JSP syntax, since it seems to be the emerging standard for server-side Java. We are currently rewriting the Servlet application to use JSPs. People who are just starting on their projects could save themselves a lot of time by using JSPs in the first place. =========================================================================== 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
