Hi! Steve Slatcher wrote: > 1) entity bean has been loaded > 2) someone modifies the database directly > 3) outofdate data is accessed by a bean client > > Anyone any suggestions for the best way to deal with this situation, > which cannot be too uncommon? Generically, or in a jboss-specific > way? You should use option B or C caching (default is A). These two modes do not cache entity data, but instead reloads from the database for each transaction. This is set by changing the container configurations (/conf/default/standardjboss.xml). regards, Rickard -- Rickard Öberg Email: [EMAIL PROTECTED] http://www.telkel.com http://www.jboss.org http://www.dreambean.com -- -------------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Problems?: [EMAIL PROTECTED]
