Re: Caching of read-only DB contents in an EJB

[Laird Nelson]

Rickard �berg wrote:
> Almost but not quite. Readonly data can be cached by stateless session
> beans. If you need read/write caching then either use Entities or a RMI
> object.

On the off chance that it's not just me:

I'm quite confused by this thread.  I was under the impression that one
of the reasons that *entity* beans exist at all in the specification is
to effectively serve as data caches for the underlying data store.  That
is, there is a person record on disk somewhere, but you deal with the
Person entity bean instead, because it will usually be (activated) in
memory.

Could someone please explain to the slow and thick among us :-) why that
is not a good idea, or why it is a less than optimal idea, or why we
should be using stateless session beans, or why we should not work with
entity beans in this problem domain, or why we should be using some
other odd beast (e.g. RMI objects) to accomplish the same thing?

Cheers,
Laird

===========================================================================
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".