Hey
jguich wrote:
> 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?
Not quite sure what you're worried about. I'm guessing that you think
that the servlet is single-threaded, yes? Well, normally a servletrunner
uses one instance of a servlet for several (possibly simultaneous!)
threads, so there's no blicking there. And the session will be
instantiated on demand, so no blocking there either.
Did this answer your concern?
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
Homepage: http://www-und.ida.liu.se/~ricob684
===========================================================================
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".
