>
> Another thought, is to use a appserver that allows reentrant
> calls into a bean controlled in the DD. IAS supports this.
Does this not violate the specification ?
> This posters problem would be non-existant. He'd just have to
> design the business logic to tolerat reentrant calls into
> the stateful session bean, which is what us server side guys
> have been doing for ages,,, until EJB came along and moved
> the complexity of client-server over the client side where
> it never was, for good reason. :) LOL, EJB, what a mess,
> now the client developers need to be the rocket scientists.
>
One of the main reasons they did not allow re-entrant calls into an EJB is
to reduce the complexity of the business code. As others have pointed out,
there are various ways in which your client side can also not be complex in
this scenario.
The major goal being that such complex stuff as threading, re-entrancy etc.
are best left with the container.
-- Aravind
===========================================================================
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".
