It occurs the spec requires ejbStore to be always called on an instance at commit time even if the instance is not dirty. Currently, we call ejbStore at sync time only if the instance is dirty.
Since persistenceManager.isModified(ctx) will not be changed, there should not be anything that could be broken by fixing this (except for many applications relying on our current implementation)? I think I'll add one more config option like call-ejbstore-only-if-dirty (making it true by default?). Other suggestions? ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
