This causes the container to flush e.g. before executing finders, which is required (and often desired) behaviour. Setting this to true will mean finders will not be aware of any modifications already made in the transaction. I'd recommend leaving it at false unless you know that your application can handle this, or unless you do many find/modify cycles on a single instance in a single transaction.
Jeremy /************************* * Jeremy Boynes * Partner * Core Developers Network *************************/ > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Corby Page > Sent: Thursday, July 10, 2003 9:45 AM > To: [EMAIL PROTECTED] > Subject: [JBoss-user] sync-on-commit-only > > > Assuming your entity beans are enlisted in a transaction, is > there any reason ever to leave this option set to false? > > Thanks, > Corby > > > > > ------------------------------------------------------- > This SF.Net email sponsored by: Parasoft > Error proof Web apps, automate testing & more. > Download & eval WebKing and get a free book. > www.parasoft.com/bulletproofapps > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/j> boss-user > ------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
