Type: Service Pack Request
Resolution: Not a bug
Affects Version/s: AOS Module 1.1.6, 5.1.1
Fix Version/s: None
Environment:Client: Windows 7 and Firefox
Server: Ubuntu, 2x CPUs and 8 GB RAM; Alfresco v5.1.1
Updating an AutoCAD DWG file on a AOS mapped share drive doesn't show the expected behaviour in terms of versioning.
The file is renamed with a different extension (.bak) and a new file is created with the original name instead.
[Steps to reproduce]:
1.) Sign up for a trail AutoDesk account at http://www.autodesk.co.uk
2.) Download AutoCAD 2017 trail here: http://www.autodesk.co.uk/products/autocad/free-trial
3.) Install AutoCAD 2017 on a Windows client and create sample drawing e.g. drawing1.dwg
4.) Set up an Alfresco One instance and log in as admin to Share
5.) Set up a site TestAutoCADVersioning
6.) Create a folder Test123
7.) Upload sample the drawing to the folder Test123
8.) Mount the Alfresco Repository, i.e. the folder created earlier, by following the instructions here: http://docs.alfresco.com/aos/tasks/aos-map-drive.html
as shared drive on the Windows client
9.) Open the sample drawing on the shared drive in AutoCAD again
10.) Make some changes to the drawing and click save
11.) The original file will be renamed as e.g. drawing1.bak and a new file will be created named as the original one (drawing1.dwg).
The latter has two versions, the first one comes from a file with the following name pattern: save[NUMBER].tmp
A new version of the original drawing1.dwg is created (1.1) on Share and also a new file called drawing1.bak with the content prior to the last modification on the shared drive
On Share you get two files drawing1.dwg and drawing1.bak, the first is showing in the version history as source file saveXYZ.tmp and stays on version 1.0.
The latter reflects the content prior to the latest update.
[Analysis to date]:
1.) Reproduced behaviour on latest Alfresco One release
2.) Screenshots attached demonstrating the issue
3.) AutoCAD file shuffle updating an existing drawing:
4.) The reported behaviour was fixed for the Webdav file services ../alfresco/webdav to handle the AutoCAD file "shuffle" when updating a drawing
according the expected behaviour.
However AOS is not using the Alfresco WebDAV implementation and it uses com.xaldon.officeservices.StandardWebdavService class instead, therefore
the fix introduced in the related JIRA hasn't been applied to the AOS implementation.