DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=35693>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=35693 Summary: Cannot Create New Objects (Rev 208532 - 2.1 Release) Product: Slide Version: 2.1 Platform: All OS/Version: All Status: NEW Severity: major Priority: P2 Component: Core AssignedTo: slide-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] The commit that removed some unnecessary forceStoreEnlistments makes it impossible to create new objects, at least with a JDBC store set to READ_COMMITTED. What appears to be happening is that by not forcing store enlistment the new object is created in a separate transaction from subsequent reads. This leads to an ObjectNotFoundException in SecurityImpl.checkCredentials() (when write permissions for the new resources are being checked) and a similar error in LockImpl.isLockedInternal(). -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
