hi!
i've started to study the approach: servlet -> ejb session -> jsp (ok, ok, now i
know that jsp = servlet).
initially, i've think that, after the servlet received a request, it could call a
session ejb and terminate.
but, since a call to the session servlet is a "normal" (rmi) call, the servlet
blocks until the ejb is done with the business logic. so, if the servlet is blocked,
how can a call to a ejb optimizes resource utilization?
initially, i thinked that the servlet could do a call to the ejb creating a new
thread and terminating, thus, the servlet would have a short life cycle. since ejb has
load balance, etc, but the servlet doesnt, i think that theres no gain with that
approach. it could be easyer to create a standard class so the servlet use it.
what i'm doing wrong?
tia,
guich.
ps: the flow in that case would be: servlet1 -> ejb -> servlet1 -> jsp . in this
case, servlet1 and jsp would free resources only when both ends?
===========================================================================
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".
