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
Abstract
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. JSP
was designed as an html extension language, which is a very bad idea.
JSP should under no circumstances be used. If you really must view
web applications as string/file processors, use Perl not Java. Perl
was designed for just that.
--
---
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, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
