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
-----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.
>
>- Phil
>
>===========================================================================
>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".
