a JSP is a servlet so let's scratch 1 and 4, since you would introduce
additional layers in the front end of the web server. Not necessary.
I would go either
1. JSP - EJB (Session beans)
2. Servlet - EJB (Session beans)
3. Both 1 and 2 depending on what kind of data you need to present.
This way you have the presentation logic in the servlets, JSPs.
You keep the business logic on your app server (EJB session beans)
In terms of scalability,
you can now easy replicate your web servers since they only hold
presentation logic.
you can cluster your business logic using the clustering techniques
provided by your EJB vendor.
Filip Hanik
Verge Sofware
jguich
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
OM.BR> cc:
Sent by: A Subject: The best approach
mailing list for
Enterprise
JavaBeans
development
<EJB-INTEREST@jav
a.sun.com>
11/22/99 10:39 AM
Please respond to
A mailing list
for Enterprise
JavaBeans
development
what is the best approach?
1. servlet -> jsp -> ejb
2. servlet -> ejb
3. jsp -> ejb
4. servlet -> jsp
thanks.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
