Thanks David! > > <!-- Descr: The passivation-strategy can be either "default" or > > "transaction". With the default setting the container will > > attempt to keep a working set of beans in the cache. With > > the "transaction" setting, the container will passivate the > > bean after every transaction (or method call for a > > non-transactional invocation). --> > > <!-- Requirements: optional --> > > <!-- Range: default, transaction --> > > <!-- Default: default --> > > <passivation-strategy>default</passivation-strategy> > > > > Omitted because: "With all four commit options the container must > > synchronize the bean instances cached state with the persistent storage > > (via ejbStore) at the end of each transaction (just before a commit is > > done) to be sure the whole transactions state is consistently persistent" > > > > isn't this one the difference between options B and C?
First, I thought about it too. And still not sure.... As I understand, the only difference between B and C is that for B ejbLoad is called only for methods running in a transaction while for C ejbLoad is called for every one. Also, ejbStore is called just before the commit of a transaction is done for all options. And as online docs says: "Never write access a bean outside a transaction context believing ejbStore will be called for synchronization, it typically will not (though somtimes it might, when the container passivates the bean) be called" So, I don't think it's definitely option B. Thus, I consider it to be C. Other thought? TIA, alex _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
