[MGNLCMIS-5] Adobe Drive cannot check files into DMS workspace Created: 01/Mar/12  Updated: 02/Aug/16  Resolved: 02/Aug/16

Status: Closed
Project: CMIS
Component/s: None
Affects Version/s: None
Fix Version/s: Backlog

Type: Story Priority: Major
Reporter: Antti Hietala Assignee: Unassigned
Resolution: Won't Do Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

CMIS module 1.0.0-SNAPSHOT, Magnolia CMS 4.5 RC 2, Adobe Drive 3


Attachments: Text File CSSServiceManager_java.log     PNG File Screen Shot 2012-06-27 at 10.33.05.png     PNG File Screen Shot 2012-06-27 at 10.36.22.png     PNG File checkin-error.png     PNG File checkout-error.png     PNG File mounted-volume-permissions.png    
Issue Links:
dependency
is depended upon by DOCU-254 Demonstrate CMIS usage with Photoshop Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Adobe Drive cannot check files into the DMS workspace. This prevents use cases such as opening a file in Photoshop, changing it and saving back into the workspace.

Adobe Drive mounts the workspace as a drive on your file system (mounted-volume-permissions.png). You can then browse the workspace using Finder or Adobe Bridge.

What works:

  • Browsing and viewing files in Finder or Adobe Bridge.
  • Creating new folders. The folders are immediately visible in Magnolia. They don't seem to require a check-in.

What doesn't work:

  • Files copy-pasted into the mounted drive are not visible in Magnolia.
  • Files saved from an application like Photoshop trigger the check-in operation which fails with "The operation could not be completed. You are not allowed to perform this operation. Error code: -6665" See Adobe-Drive-checkin-error.png and CSSServiceManager_java.log.
  • Checking out an existing file fails with "The operation could not be completed. The operation would make a conflicting change to an item that is already checked out. Error code: 6". See checkout-error.png.

Accessing the CMIS repository is very CPU intensive. The Java process that Magnolia launches peaks as soon as you navigate the workspace.



 Comments   
Comment by Tobias Mattsson [ 02/Mar/12 ]

We raised a question on Adobe Drive forum for these problems
http://forums.adobe.com/message/3962855

This is what's being said on the Chemistry user-list
http://mail-archives.apache.org/mod_mbox/chemistry-dev/201110.mbox/%3C4E930AD7.2080104@alfresco.com%3E

Comment by Antony Hutchison [ 26/Jun/12 ]

I've done some tests with this using

Magnolia 4.5.3
Adobe Drive 4
CMS 1.1.0-SNAPSHOT
Hosted on a Linux VM running in VMWare Fusion 4 on OSX 10.7

Mac Finder gives error -36 when trying to copy a file in.
I can copy the file in using Terminal using the mounted drive, i.e /Volumes/MyMagnoliaCmis/... but it doesn't appear in the CMS at all. It's in the Terminal file listing but not in the new folder in the CMS.

I can create and delete folders from the Finder but it's all terribly slow. Files delete quickly from the Finder if added using Terminal.

Console.app gives this output when adding via Finder:

26/06/2012 19:06:23.559 mds: (Error) FMW: FMW FSE_CREATE_FILE uid/gid -1 /Volumes/MagnoliaDevVM/Demo/Screenshots/image2.png
26/06/2012 19:06:23.577 mds: (Error) FMW: FMW FSE_STAT_CHANGED uid/gid -1 /Volumes/MagnoliaDevVM/Demo/Screenshots/image2.png
26/06/2012 19:06:23.577 mds: (Error) FMW: FMW FSE_FINDER_INFO_CHANGED uid/gid -1 /Volumes/MagnoliaDevVM/Demo/Screenshots/image2.png
26/06/2012 19:06:23.838 mds: (Error) FMW: FMW FSE_XATTR_REMOVED uid/gid -1 /Volumes/MagnoliaDevVM/Demo/Screenshots/image2.png
26/06/2012 19:06:23.849 mds: (Error) FMW: FMW FSE_XATTR_MODIFIED uid/gid -1 /Volumes/MagnoliaDevVM/Demo/Screenshots/image2.png
26/06/2012 19:06:23.865 mds: (Error) FMW: FMW FSE_XATTR_MODIFIED uid/gid -1 /Volumes/MagnoliaDevVM/Demo/Screenshots/image2.png
26/06/2012 19:06:28.928 mds: (Error) FMW: FMW FSE_CONTENT_MODIFIED uid/gid -1 /Volumes/MagnoliaDevVM/Demo/Screenshots/image2.png

but this when via Terminal:

26/06/2012 19:21:41.878 mds: (Error) FMW: FMW FSE_CREATE_FILE uid/gid -1 /Volumes/MagnoliaDevVM/Demo/image3.png
26/06/2012 19:21:41.878 mds: (Error) FMW: FMW FSE_CHOWN uid/gid -1 /Volumes/MagnoliaDevVM/Demo/image3.png
26/06/2012 19:21:41.878 mds: (Error) FMW: FMW FSE_CHOWN uid/gid -1 /Volumes/MagnoliaDevVM/Demo/image3.png
26/06/2012 19:21:41.897 mds: (Error) FMW: FMW FSE_XATTR_MODIFIED uid/gid -1 /Volumes/MagnoliaDevVM/Demo/image3.png
26/06/2012 19:21:41.897 mds: (Error) FMW: FMW FSE_CHOWN uid/gid -1 /Volumes/MagnoliaDevVM/Demo/image3.png
26/06/2012 19:21:41.908 mds: (Error) FMW: FMW FSE_CONTENT_MODIFIED uid/gid -1 /Volumes/MagnoliaDevVM/Demo/image3.png

Same image, different file name. It is a different sequence. I've not seen any options yet to increase the verbosity of the logs - how did you get the attached log from Adobe Drive?

'mds' is part of Spotlight: I added the volume as an exclusion to the indexer, but without any change.

The image I uploaded via Terminal was a screenshot; xattr was able to read the metadata from this, although I don't know if this is some trick with the Adobe Drive and local caching. I tried with offline-mode enabled and disabled without any notable effect.

I don't think there is enough information here to solve but it might help work out how to move this forward.

Comment by Antony Hutchison [ 27/Jun/12 ]

I'm now trying it with an alternative client - CMISSpacesAir

http://code.google.com/p/cmisspaces/downloads/detail?name=CMISSpacesAir-2012.04.19.air

This also does not successfully upload a file. I've also tried the Magnolia CMIS module with Chemistry OpenCMIS Workbench 0.7.0-full - this reports that Magnolia is not a compliant to the CMIS specification. Open the workbench, log in using AtomPub, select any item, and hit 'check specification compliance'.

It appears the module is using Chemistry 0.6.0; I will check with a newer version.

Screenshots attached.

Comment by Antony Hutchison [ 27/Jun/12 ]

Chemistry Workbench 0.7.0 spec conformance check failures; screenshots attached.

Comment by Michael Mühlebach [ 02/Aug/16 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 00:00:50 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.