that would be the only case where I can see that you could bypass RMI. How
it would be done and maintain within spec would be beyond me. since the
client is not run in the container... certainly in the case of a session
bean calling Entities yes, but in the case of a web client (servlet or
whateve
> Al Fogleson wrote:
> > then you start adding all the RMI calls over the network and that adds
> some load too
>
> Well, EJBs will not always be called remotely to start with. A very
> common scenario is that you write Servlets/JSPs that communicate with
> EJBs. Usually you will run your Web co
Karl;
Most of the EJB containers I have tried out have multiple instances of a JVM
running, thats an awful lot of overhead. We are also running applications
where there are up to (and sometimes more) than 100 simultaneous accesses on
a bean. Even using clustering there is still an awful load on o
Hello Al,
Al Fogleson wrote:
> Yes and no. There is a terribly large amount of overhead involved in
EJB to begin with
Which overhead are you referreing to by this? The overhead involved
should be low compared to the optimizations that are done to speed up
data access.
> then you start adding a
