Youre absolutely right about it's not a checkin request. The first time a document is added for versioning in Adobe Drive they perform a "Check In", which I believe, is similar to a Document Creation request.
I think they expect some thing in order to proceed but I have no clue what it is. Since the operation fails, there are no subsequent PUT requests. On Sun, Mar 27, 2016 at 7:34 PM, Florian Müller <f...@apache.org> wrote: > Hi, > > This is not a checkin request. This is an invalid create document > request. (The property cmis:name is missing). > Could you please check if there is a PUT request against the PWC > resource? That would be the checkin call. > > - Florian > > > > Hello Florian, I'm extremely appreciate that you take time to reply. > > > > I just tested again the InMemory Latest Build. What I tried is to > > checkin a new file called "test.txt". > > > > I also tried to capture the POST request using rawcap, basically they > > send out an /POST > > /inmemory/atom/A1/children?id=125&versioningState=checkedout / > > / > > / > > with the body being > > > > / <?xml version="1.0" encoding="utf-8"?> > > / > > /<entry xmlns="http://www.w3.org/2005/Atom"/ > > /xmlns:cmisra="http://docs.oasis-open.org/ns/cmis/restatom/200908/"/ > > /xmlns:cmis="http://docs.oasis-open.org/ns/cmis/core/200908/";>/ > > / <title>test.txt</title>/ > > / <cmisra:object>/ > > /<cmis:properties>/ > > /<cmis:propertyId propertyDefinitionId="cmis:objectTypeId">/ > > /<cmis:value>cmis:document</cmis:value>/ > > /</cmis:propertyId>/ > > /</cmis:properties>/ > > / </cmisra:object>/ > > /</entry>/ > > > > Again we got an error with the relevant Log in Adobe Drive 5: > > > > com.adobe.drive.data.model.DriveException: Error checking in: Conflict > > at > com.adobe.drive.internal.data.manager.DataManager.executeCheckIn(DataManager.java:5680) > > at > com.adobe.drive.internal.data.manager.DataManager.checkIn(DataManager.java:5305) > > at > com.adobe.drive.internal.data.manager.DataManager.checkLocalAssetPostClose(DataManager.java:10324) > > at > com.adobe.drive.internal.data.manager.DataManager.close(DataManager.java:3423) > > at > com.adobe.drive.internal.biz.filesystem.FileSystemService$10.execute(FileSystemService.java:839) > > at > com.adobe.drive.internal.biz.filesystem.FileSystemService$10.execute(FileSystemService.java:1) > > at > com.adobe.drive.internal.biz.filesystem.FileSystemService$FSCallable.run(FileSystemService.java:1793) > > at > com.adobe.drive.data.internal.persistence.PersistenceRunner$2.runWithTransaction(PersistenceRunner.java:186) > > at > com.adobe.drive.data.internal.persistence.PersistenceModificationCallable.run(PersistenceModificationCallable.java:71) > > at > com.adobe.drive.data.internal.persistence.PersistenceRunner.run(PersistenceRunner.java:119) > > at > com.adobe.drive.data.internal.persistence.PersistenceRunner.runWithTransaction(PersistenceRunner.java:181) > > at > com.adobe.drive.internal.biz.filesystem.FileSystemService.runWithTransaction(FileSystemService.java:1748) > > at > com.adobe.drive.internal.biz.filesystem.FileSystemService.runWithTransaction(FileSystemService.java:1727) > > at > com.adobe.drive.internal.biz.filesystem.FileSystemService.close(FileSystemService.java:821) > > at > com.adobe.drive.ifs.job.CloseHandler$1.call(CloseHandler.java:67) > > at com.adobe.drive.ifs.job.CloseHandler$1.call(CloseHandler.java:1) > > at com.adobe.drive.model.context.Context.run(Context.java:88) > > at > com.adobe.drive.ifs.internal.IFSConnection.dispatch(IFSConnection.java:187) > > at > com.adobe.drive.ifs.internal.IFSConnection.run(IFSConnection.java:142) > > > > It;'s frustrating with AD5 really since I have no Idea what they are > > expecting after that call. > > > > On Sun, Mar 27, 2016 at 4:54 PM, Florian Müller <f...@apache.org > > <mailto:f...@apache.org>> wrote: > > > > Hi, > > > > Do you think you can capture this POST request? > > I don't think this is an OpenCMIS server framework problem, but we > > should check. At least the InMemory server should be more robust. > > > > - Florian > > > > > > > Hello everyone, > > > > > > I know it's not a Adobe Drive 5 (AD5) place but i'm pretty > > desperate now > > > trying to uderstand the underlying actions. I would be very > > grateful if > > > someone knows how the checkin new files works for AD5 (latest > > build)? > > > > > > It does not seem to work with the latest build from Alfresco and > the > > > InMemory OpenCMIS server. The one from InMemory got an > > NullPointerReference > > > error while Alfresco produces an empty file and an other emoty > > PWC, and AD5 > > > has an Not Allowed Action Error. > > > > > > I seems to me that it sends a POST request to the parent > > folder's children > > > service with a checked out requests but without any content. > > Why is that? > > > It seems also expect a Private Working Copy > > > > > > Thanks very much in advance. > > > > > > > > >
