Create and remove on read-only beans

Question

while playing around with read-only beans i found that calling create()
ond read-only homes and remove on read only entities does work, which
was new to me. 'work' just means changing the database ;)
ist there any danger in using this (maybe just an internal feature which
does not work in 7.0, ...) ?
axel.

Answer 1

You should definitely check out 7.0 and its support for optimistic caching. It
does what you want.
-- Rob
Axel Großmann wrote:
thanks for the quick response.
Rob Woollen wrote:
ist there any danger in using this (maybe just an internal feature which
does not work in 7.0, ...) ?
No, it'll work fine. Until 7.0, read-only beans always ran in an
unspecified transaction. In 7.0, this has been relaxed to allow you to use
all the tx attributes with read-only beans.sounds great; seems that we should give 7.0 beta a try.
what comes to my mind is: if read-only beans would also write changes to
their CMP fields to the database (and send invalidation message) we
would have some kind of write-through-caching bean, wouldnt we ?
this is actually what I'm searching for, since we have to port an
application to weblogic with was designed using one bean per business
object - mapping this to the two-bean read-mostly pattern without
changing the present logic seems impossible without many changes and
loosing the ability to run on other application servers too.
so why not a 'read-mostly-bean' instead of manually implementing it ?
axel.--
AVAILABLE NOW!: Building J2EE Applications & BEA WebLogic Server
by Michael Girdley, Rob Woollen, and Sandra Emerson
http://learnWebLogic.com
[att1.html]