LERBSCHER wrote:
>
> Hi,
> If applications customers tries to reach one " entity bean " identified
> by the same key, how the container EJB manages the rival accesses to the
> EJB (in a deal or outside a transactional context)?
> Is it a specific behavior in the container or it(he) is to normalize by
> the specification EJB?
> Thank you
> Jean-Pierre
>
Outside a transaction context, all clients use the same bean instance. No
synchronization is done, except if you have specified that your bean is
not "Reentrant" (see .xml file). In that case, accesses are serialized.
If you are inside transactions, the container manage the transaction isolation by
allowing
a particular instance of the bean for each transaction.
Anyway, you never have at the same time an instance asccessed outside a transaction
and inside a transaction, for obvious problems : It's the container job to
avoid this.
Moreover, since jonas 2.3 (not released yet), we do not allow to mix up these
transactions because it was too difficult to cup with specific transaction isolation
of each type of database. Most of the database do not support all transaction
isolation levels, or raise exceptions if 2 transactions occur at the same time,
sometimes even on different objects!
Another point is that the "Reentrant" tag was not taken into account in jonas 2.2
This has been changed in jonas 2.3.
I hope this answer your question...
--
Philippe Durieux ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Bull - 1 rue de Provence - 38432 Echirolles Cedex France
[EMAIL PROTECTED]
-> Download our EJBServer at http://www.evidian.com/ejb <-
----
This list is cross-posted to two mail lists. To unsubscribe,
follow the instructions below for the list you subscribed to.
For objectweb.org: send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe ejb-container-group".
For enhydra.org: send email to [EMAIL PROTECTED] and include
in the body of the message "unsubscribe ejb-container-group".
