check out SessionSync interface in ejb spec, its purpose is caching of data
without comprimising integrity...
however, remember that MOST app servers AREN'T truly aware of other JVM's
running in a cluster config, etc, so
cross JVM / host syncronization isn't always possible (thus rendering it
inappropiate at most times, but some
very particular cases may be worth the hassle)
My 2c,
JP
-----Original Message-----
From: Heiko Gottschling [mailto:[EMAIL PROTECTED]]
Sent: Martes, 09 de Enero de 2001 13:21
To: [EMAIL PROTECTED]
Subject: Re: Please comment: Using java.lang.reflect to simplify
database access
Hi,
> Assuming a usual situation where you will access objects of any
> particular class a significant number of times, then cache most of the
> reflection results by class. In particular, you could cache the
> PreparedStatement and the list of Field objects.
Haven't thought of that. Bringing up the issue of a cache: how would a cache
be implemented in a session bean? As I understand, the container always has
some session bean instances handy, how could these be made to share the same
cache? Usually, I would solve such a problem with static fields/methods, is
this possible in a session bean?
thx
Heiko
===========================================================================
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".
