Re: JSP vs ASP

[pluta@xxxxxxxxxxxxxxxxxx]

rstearns wrote:

>The JSP really allows the presentation layer to be managed by the HTML gurus
and
>the business logic layer to be managed by the Java/Servlet gurus.
---------

That's probably the most concise definition of the JSP/servlet architecture.
The biggest problem with any of the other HTML-based technologies such as CGI or
ASP is that you had to have a new skillset: you needed someone who could both
write business applications and knew HTML inside and out.  CGI puts HTML into
legacy applications, while ASP puts VB programming into HTML pages (yeah, I know
ASP supports JavaScript, but the overwhelming majority of programming is done in
VB, a completely DIFFERENT issue which I refuse to rant about in this post).

Okay, so what makes JSP different?  JSP can almost completely separate the two
skills.  In the simplest example, the HTML guru can write a simple HTML page
that, say, prints the user name and city.  He gets the city with a JSP tag that
performs a call to a JavaBean.  The JavaBean is written by a programmer who
understands the database, but knows nothing about HTML.

This example can be extended, especially with servlets.  When using a servlet,
the servlet can instantiate the beans depending on the session chracteristics
and then execute a JSP page.  This way, the page can change content dynamically
with absolutely no programming from the HTML guru.

Joe Pluta
www.zappie.net



+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---