Community
Participate
Working Groups
This bug has been created for the backport of the fix for bug 249544 to go into the TM 3.0.2 release.
Created attachment 114607 [details] patch for waiting for final timestamp This patch is a straight back-port from what we have in HEAD.
Created attachment 114795 [details] updated patch to deal with compatibility issues with old IBM dstore server
Created attachment 114796 [details] updated patch to deal with compat issues with old IBM dstore server
Created attachment 115398 [details] updated patch to ensure original timestamp is the original
Created attachment 115401 [details] another update to let the wait method timeout
Created attachment 115408 [details] another update to also check that monitor isn't cancelled
Created attachment 115693 [details] patch dealing with remote file cache
Created attachment 117341 [details] updated patch Here's the updated backport patch.
SystemUploadConflictAction.BackgroundSaveasJob.run() We do: // copy temp file to remote system fs.upload(_tempFile.getLocation().makeAbsolute().toOSString(), _remoteFile, SystemEncodingUtil.ENCODING_UTF_8, monitor); why was this changed to _remoteFile instead of _saveasFile? Otherwise code review seems okay. Need to test it out after hearing about above.
Created attachment 117370 [details] update to the SystemUploadConflictAction.BackgroundSaveAsJob Adding this patch to ammend SystemUploadConflictAction.BackgroundSaveAsJob since we shouldn't be passing in _remoteFile (it should be _saveAsFile).
Review +.
I've committed the changes to cvs.
(In reply to comment #12) > I've committed the changes to cvs. > updated to match the HEAD.