Hi Sundar.
the ejb server maintain it according to "commit-option" you deploy it with.
for example :
if you "promise" your bean its data will never be touched outside of the ejb
server scope, which means it can use cached data whenever possible, you
deploy it with commit-option A.
if not, you should use commit-option B or C and then it synchronize the data
accordingly (Im not sure what the differences are, check in ejb-spec about
it, or search the mailing list archives, there was a lot of discussion about
this issue)
Shahar
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Sundar Rajan
Sent: Thursday, January 18, 2001 10:02 PM
To: [EMAIL PROTECTED]
Subject: [jBoss-User] Refreshing the cache
How does EJBs maintain its data synchronized with the database? How can
I refesh the data if updates to the database are done outside of the ejb
context (say using some client server tools). I do see at some point in
time they do get refreshed, but if I want to see the changes immediately
after updating the database, how can I force the EJBs to load itself
again?
Thanks
Sundar
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
