> here are the statistics:
>
> jsp -> ejb : Tom, Filip, Tye, Vivek, Ian : 5 votes
>
I vote for it to..
> servlet -> ejb -> jsp : Eric, Sachin, Javier : 3 votes
> servlet -> jsp -> ejb: Vivek, GUICH : 2 votes
Do not make no sense because JSP (code in HTML) are converted to servlets (HTML
in code)
> 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
>
Yes..
JSP can handle classics Beans and custom tags so minimum presentation code is
included in JSP.. See Tomcat
> 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.
What about Tag extensions for JSP? (JSP 1.1)
St�phane
===========================================================================
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".
