I'm wondering what would happen if an entity bean were instantiated,
representing some data in the database, and another non-EJB client, say a
Perl script, updates the information in the db that the bean represents.
Can the container be told to continually watch changes made in the db, or
more specifically, does Borland's AppServer support this capability? Can
an entity bean somehow be setup to never cache data from the db, and then,
through use of a deployment descriptor, have its caching capabilities
"switched on"?
-M@
--
Matt Hixson
Aventail Corporation
Seattle, Washington
www.aventail.com
===========================================================================
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".
