hi,
thatz not exactly what i tried. i accessed the same record which was represented using
entity bean .
also i was using container managed transaction , so i did not explicitly commit the
transaction .
but i was able to access the same record thru multiple cients (read and also update).
Also i could update the same record through multiple clients . the updated record
relected the last request among all the clients.
parikshit
-----Original Message-----
From: RAVIKHANDELWAL [SMTP:[EMAIL PROTECTED]]
Sent: Friday, November 12, 1999 12:39 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Entity Beans in EJB
Hi Parikshit!
Thanx for your reply.
I have one more question.
This is regarding the 3rd query that I raised about TX_SERIALIZABLE.
Let one client access the entity bean and using a set method set a value in
the entity bean. Do not commit the transaction yet.
Let another client using JDBC thru a session bean read the data
corresponding to the earlier entity bean.
Will he read the changed value.
Regards
Ravi
> -----Original Message-----
> From: Parikshit Pol [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, November 12, 1999 11:45
> To: [EMAIL PROTECTED]
> Subject: Re: Entity Beans in EJB
>
>
> ****** Message from InterScan E-Mail VirusWall NT ******
>
> ** No virus found in attached file noname
>
> Mail Scanned For Virus At ITLInfosys
>
> ***************** End of message *************** << File:
> ATT561173.txt >>
===========================================================================
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".
