I recommend you consider using soft locks. Row locks in a world of short
transactions and JDBC connection pools are not going to work well for you.
There is a lot of information on the archives of this list on the topic.
Also we are documenting this and other patterns in our upcoming Developer's
Guide. You can register for this at our WEB site.
-Chris.
> -----Original Message-----
> From: Thomas Hofmann [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, January 24, 2000 11:48 AM
> To: [EMAIL PROTECTED]
> Subject: Entity Bean and row locking
>
> Hi,
>
> I have one simple question:
>
> Assume there are an entity bean A and two users (clients) U1 and U2. U1
> finds the bean A with ejbFindByPrimaryKey(PK). He intends to update the
> data represanted by bean A.
> How can U2 be informed that bean A will currently be updated by another
> user (must U1 do a ORA SELECT FOR UPDATE in the ejbFind.. method see
> above)? U2 should be able to read the data but he has to know that he
> cannot change the data (He is reading old data). If I use isolation
> level "TRANSACTION SERIALIZABLE" then U1 won't be able to read the data,
> will it ?
>
>
> Any help will be appreciated
>
> --
> Thomas Hofmann
> BSP Partners: Entwicklung und Vertrieb f�r
> Bankingsoftware und Banksysteme GmbH & Co. KG
> Tel. : (+49) - (0) 93 71 / 40 88 - 71
> Fax. : (+49) - (0) 93 71 / 90084 - 71
> mailto:[EMAIL PROTECTED]
>
> ==========================================================================
> =
> 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".
