i am confused about how things will be handled in both the cases when one of
the clients ( all of them accessing the same row) of entity bean chooses to
delete the row by calling remove().
what happens to the other clients having the reference?
-----Original Message-----
From: Avi Kivity [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 23, 2000 11:06 PM
To: [EMAIL PROTECTED]
Subject: Re: one instance of any given entity bean?
> -----Original Message-----
> From: Adena Galinsky [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 23, 2000 17:59
> To: [EMAIL PROTECTED]
> Subject: one instance of any given entity bean?
>
>
> I seem to have read conflicting reports of this:
>
> Is it true that there is only ever 1 instance of a particular
> entity bean?
>
> In other words, if there are three rows in a table,
> representing Bob, Jim,
> and Tom,
> and we have an entity class called Person,
> there will only ever be one Person instance containing the
> values from
> Bob's row?
>
> Or could there potentially be 3 instances each representing Bob?
>
It depends on your container. Those which use optimistic concurrency control
allow multiple Bobs to exist concurrently, each in its own transaction
scope. Those which use pessimistic concurrency control allow a single Bob.
Some servers mix the models, allowing a single Bob per JVM, but multiple
Bobs overall, thus making you suffer from the deficiencies of both models.
- Avi
--
s/\be(\w+)/e-\1/g;
===========================================================================
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".
===========================================================================
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".
