You make your decision sound like it's either or. In fact you have options!
=) I've been fortunate to have the opportunity to implement 3 systems
using a hybrid to your statement...JSP (jhtml in older days) to display the
dynamic data that so many web pages require --> Servlets to act as a proxy
to --> EJB's for persistence of business object data. The beauty of JSP is
that is furthers the seperation of presentation from business logic. This
is important as it allows non-programmers to focus on their specialty
(cognitive/creative or whatever) creating the surrounding html
content/structure. Your experienced Java developers are left to
design/develop the n-tiers that represent the business logic required by the
problem domain. This responcibility delagation is furthered by the use of
application servers (Weblogic, Dynamo, Websphere, etc.), which handle ALOT
of low-level system services that are often
difficult/expensive/time&resource intesive efforts when custom built. Yes,
App servers cost alot up front, but I truely believe your investment is
recovered, with less risk, quicker than the alternative. After attending an
Enterprise Java Architect Planning & Design course from Sun my beliefs have
only been solidified.
Another key thing to remeber is that jsp files ARE SERVLETS. In fact it is
a PageCompileServlet that Sun introduced over 1 1/2 years ago. Behind the
scenes the servlet/jsp engine converts the *.jsp to a *.java file, compiles
the generated source file to bytecode then loads the class into the vm &
executes the service method.
hello.jsp turns into -->
<code>
// Generated by JRun, do not edit
package jsp;
import java.io.*;
import java.util.*;
import java.net.*;
import java.beans.*;
import javax.servlet.*;
import javax.servlet.http.*;
import javax.servlet.jsp.*;
import com.livesoftware.jsp.*;
import com.livesoftware.scripting.*;
public class hello extends HttpJSPServlet implements JRunJspPage
</code>
Hope this helps in your decision,
Jon
----- Original Message -----
From: Carlos J. Herrera <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, October 06, 1999 5:45 PM
Subject: Java Servlets vs. JSP
> My group is trying to decide whether to use Java Servlets
> or Java Server Pages to build a MyExcite or MyNetscape
> type of site.
>
> We have previously worked with Servlets and have
> successfully installed and used
> Apache 1.3.6,
> JDK/JRE 1.2.1,
> JSDK 2.0,
> and JServ 1.0.
>
> What else would we need for the JSP environment?
>
> What are the pros and cons of JSP over Servlets?
> Learning Curve? Suggested Books
> HTML? Removing the HTML design from the code
> Java Beans? Accessibility of Enterprise Java Beans
> Applets? Is there an HTTP Tunneling variant for JSP?
>
> And..
> Personal comments on JSP vs Servlets would be very helpful.
>
> __Carlos__
> [EMAIL PROTECTED]
>
>
___________________________________________________________________________
> 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
>
___________________________________________________________________________
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
