On Tue, 2004-01-06 at 22:19, Bill Burke wrote: > Currently the default entity bean locking strategy is Commit 'B' plus > pessimistic. If we're going to default to 'B', can we default to multi > instance? >
+1 from me It doesn't make sense to serialize access to a "shared" instance whose data won't be reused anyway. Its only utility is <read-only> in CMP. i.e. ignore the server's request to reload data for an already associated bean. Regards, Adrian > Bill -- xxxxxxxxxxxxxxxxxxxxxxxx Adrian Brock Director of Support Back Office JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
