reposting (i did not received!)
Hi,
thanks for all that answered.
here are the statistics:
jsp -> ejb : Tom, Filip, Tye, Vivek, Ian : 5 votes
servlet -> ejb -> jsp : Eric, Sachin, Javier : 3 votes
servlet -> jsp -> ejb: Vivek, GUICH : 2 votes
So', i think that jsp -> ebj wins.
Trying to expand these 3 possibilities:
a) jsp -> ejb
1) the browser sends data to the jsp
2) the jsp calls a SFS or a SLS (stateless session) that has the business logic,
and fetches data from db. it then sends the data back to the jsp
3) jsp sends the data back to the page
b) servlet -> ejb ->jsp
1) the browser sends data to the servlet. this one manages the session
2) the servlet calls a StateFul Session (SFS) EJB that has the business logic.
This SFS access the db and create beans to the jsp. stateful or stateless?
3) the jsp uses this beans to create the presentation, and send it directly to the
browser
c) servlet -> jsp -> ejb
1) browser sends data to the servlet. this one manages the session, security,
etc.
2) the servlet sends the parameters to jsp
3) the jsp gets data from a Entity EJB, creates the html and send back to the
browser.
is this really what you (all) think?
ps: before this discussion, i would vote on (c). after thinking a while, i think that
(b) instead of (c) is the best way, because:
1. it lets the servlet do what it really knows how to do: manage session's, security,
etc
2. it uses ejb to handle the busines logic with state??? sessions
3. it lets we create a framework of generic jsp outputs.
ps2: is a good approach servlet (with business logic) calling jsp directly?
ps3: i'm thinking in creating a good framework for lowering the maintenance cost.
===========================================================================
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".
