Good thing you sent this on a holiday weekend. :)
At any rate, I agree with the statement that Java should be used as Java,
and not deficient Perl - but I *do* take slight issue that JSP encourages
the latter behavior. To a degree it does, sure - but nobody with experience
in Java thinks that JSP is more than a convenient mechanism for rendering
data (along with some capability for generating it.) Those who don't think
that... well, even they can get things done, a testament to the relative
genericity of JSP.
As far as broad adoption... post to usenet, post to slashdot, post to
javalobby, post to freshmeat, post to the mailing lists. Good luck replacing
JSP in J2EE... and I disagree with your statement that JSP encourages the
view of data as anything other than what it is. Sounds like an axe is being
ground ("I invented somethin'! Come lookie here!") and I'd be interested in
how you arrived at the conclusion, because the only limitation JSP has in
this area is forced upon it by the rendering engine.
>From: Brad Cox <[EMAIL PROTECTED]>
>Reply-To: A mailing list about Java Server Pages specification and
>reference <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Just say no to JSP
>Date: Sat, 26 May 2001 17:04:49 -0400
>
>I've just completed a major revision of the WAP software and
>articles that were published in the last two month's Dr. Dobb's
>Journal.
>
>The software and articles are available at
>http://virtualschool.edu/wap. The demonstration application isn't
>working there yet (tomcat configuration still underway).
>
>Please check it out. I welcome all comments, particularly suggestions
>as to how to get this approach broadly adopted.
>
>Just say no to JSP
>
>Perl and JSP encourage the view that web pages are files, links are
>file names, and request and database fields are strings. But although
>html does represent everything as data, html is a restriction on
>browsers, not web applications.
>
>Java should be used as a fully object-oriented language, not as a
>deficient Perl. Pages should be page objects, links between pages
>should be messages between objects, and fields should be instances of
>application-specific fields that encapsulate the ability to validate
>user input.
>
>WAP was developed and tested with the Apache/Tomcat/JServ servlet
>engine but should work with others such as Resin. If the engine
>supports JSP it is not used. The software replaces the sole useful
>feature JSP provides with the MLS preprocessor described below.
>--
>---
>For industrial age goods there were checks and credit cards.
>For everything else there is mybank.dom at http://virtualschool.edu/mybank
>Brad Cox, PhD; [EMAIL PROTECTED] 703 361 4751
>
>===========================================================================
>To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
>JSP-INTEREST".
>For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST
>DIGEST".
>Some relevant FAQs on JSP/Servlets can be found at:
>
>http://java.sun.com/products/jsp/faq.html
>http://www.esperanto.org.nz/jsp/jspfaq.html
>http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
>http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
