On Tue, 2003-12-09 at 13:10, Dies Koper wrote: > Hello Pedro, > > I was just reading something about that today. Search for the Seppuku > pattern on theserverside.com. It exploits the rule that when a > RuntimeException is thrown and uncaught in a bean, the container throws > the instance away. > I hope that is what you are looking for. > > Regards, > Dies >
I know there exist the read-mostly pattern for most of j2ee implementations. However, I'm wondering how to invalidate *all* the instances of a entity bean? I would like to know how the invalidateAll() is implemented on weblogic? Should it be a search for all the read-only entity beans instances and run a method that would throw a exception? Should it be like that? Isn't expensive or is the only way to do it? thanks, regards, Pedro Salazar. > > Pedro Salazar wrote: > > > > Greetings, > > > > how can I invalidate a cache of entity beans? Is it possible to do it > > only for a specific instances? > > > > BTW, a read-only and a read-write views for the same entity beans where > > the update of a read-write entity bean would invalidate the read-only > > entity beans. It's possible and how? > > > > thanks. > > > > regards, > > Pedro Salazar. -- PS [EMAIL PROTECTED] PGP:0E129E31D803BC61 =========================================================================== 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".
