----- Original Message -----
From: Jean-Baptiste Nizet <[EMAIL PROTECTED]>
> > As a simplified example (pseudocode):
> >
> > Stateless Session Bean
> > =======================
> > public void incrementValue(int pk) {
> > entityBeanRemote = entityBeanHome.findByPrimaryKey(pk);
> > int value = entityBeanRemote.getValue();
> > value++;
> > entityBeanRemote.setValue(value);
> > }
> I don't follow you here. Are all the calls in the above methods done in a
single
> transaction or not?
Yes, they are executed in a single transaction.
> If they are, then IAS, using the verifyModifiedFields or verifyAllFields
flag,
> can detect that the data have been changed by another transaction and
throw an
> exception instead of updating the value.
But not in a BMP situation (that is why I mentioned ejbStore, dependent
objects, etc. earlier). In applications that I have been involved in, only
10%-20% of our entity beans are able to be represented as single table-bean
CMP entities. This dialogue is also meant for persons using other containers
as well, not to get bogged down in the proprietary semantics of a praticular
engine.
I personally like what IAS does for CMP beans, but I am curious [not
doubtful :-)] if they can extend their persistence architecture to
multiple-table entity beans.
jim
===========================================================================
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".
