> BTW Andrzej, in case you start thinking that Craig's design
> model, as he describes it below, is odd, or different, and
> thus to be avoided, I would encourage you to adopt it.
And it seems to fit in well with the new J2EE Application
Programming Model, available for preview now at:
http://developer.java.sun.com/developer/earlyAccess/j2sdkee/download-docs.html
Also, on the general topic of Servlet/JSP architecture,
I don't know yet if it's a good idea or not, but I am
tending to like the idea of not having URLs in HTML pages
point to actual pages/servlets, but instead just having
the URL be some command string which might only make sense
to the dispatching servlet - enough to figure out where to
dispatch the request. Also, for some reason I prefer the
idea of precompiling JSP pages and deploying them as servlet
classes, rather than deploying the raw JSP text pages and
compiling them on the fly when they are first requested,
as seems to be popular; I don't see why I want to be
doing that any more than deploying my whole application as
Java source and letting the application/web server figure
out what to compile as it goes along, while the user waits.
But then again, I have no idea what I'm talking about. :)
Larry
===========================================================================
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
