Tom Valesky writes:
> Wouldn't that violate the Isolation property of transactions (i.e.
> changes not visible outside the transaction until the transaction
> commits)?
>
> Tom Valesky -- [EMAIL PROTECTED]
> http://www.patriot.net/users/tvalesky
Nope, its the _same_ transaction, see original message below.
I'm a few days behind this thread (and disconnected for a while) but
I'll add my weight to Imre Kifor's succinct description of correct
transactional semantics.
In any transaction, including distributed ones, you should see the
committed state plus the effects of changes made earlier within the
same transaction. Outside the transaction you should only see the
committed state.
The behaviour clearly requires a lot of ejbStore/ejbLoads to ensure
correct behaviour and consequently efficient implementations need very
tight intergration between the EJB server and database. There are
clear potential efficiency speed-ups if, for example, a container
knows it has exclusive acces to a database.
I've played with few commercial EJB servers - any vendor like to
comment on whether they support proper transactions? What efficient
tuning do they allow over and above the spec. I guess at least Ejipt
does The Right Thing.
- Phil
> -----Original Message-----
> From: Philip Aston <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> Date: Friday, October 08, 1999 4:57 AM
> Subject: Re: finder methods specifications
>
>
> >Rickard �berg writes:
> > > Philip Aston wrote:
> > > > Whatever, surely the container should _support_ finding an
> > > > entity that was created in the same transaction?
> > >
> > > Yes, the create should (AFAIK) do a "insert" call to the db, so
> > > any finders within the same tx should see the new entity, and
> > > hence be able to find it.
> > >
> > > That said, I would still like to see why the create and find
> > > must be done in the same tx.
> > >
> > > /Rickard
> >
> ><fantasy>
> >
> > Perhaps the transaction involves two independent beans. Unknown
> > to the client or each other, each bean needs to access an entity,
> > creating it if it doesn't exist.
> >
> ></fantasy>
> >
> >Actually, this doesn't seem too far fetched.
===========================================================================
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".
