-
1. Re: Rename, New folder action using Drive CMIS connector
Gang_Z Sep 28, 2012 1:24 AM (in response to mandarpkulkarni@gmail.com)Hi,
Please don't add/move files and folder under the root folder of the mounted drive, currently, there is a design limitation here, thanks
Gang
-
2. Re: Rename, New folder action using Drive CMIS connector
mandarpkulkarni@gmail.com Sep 28, 2012 2:09 AM (in response to Gang_Z)Yes, I am aware of that limitation. But I have seen this behavior even inside other folders on the mounted drive.
-
3. Re: Rename, New folder action using Drive CMIS connector
Gang_Z Sep 28, 2012 2:14 AM (in response to mandarpkulkarni@gmail.com)Please post the log here, then we can do a quick check
Thanks
-
4. Re: Rename, New folder action using Drive CMIS connector
mandarpkulkarni@gmail.com Sep 28, 2012 2:43 AM (in response to Gang_Z)Logs on "Rename" action
2012/09/28 05:34:58,691 [IFSConnection-1] FATAL IFSConnection - NASTY Runtime exception for Request: RENAME
com.adobe.drive.biz.filesystem.FileSystemException: java.lang.NullPointerException
at com.adobe.drive.internal.biz.filesystem.FileSystemService.run(FileSystemService.java:1680 )
at com.adobe.drive.internal.biz.filesystem.FileSystemService.run(FileSystemService.java:1646 )
at com.adobe.drive.internal.biz.filesystem.FileSystemService.rename(FileSystemService.java:9 81)
at com.adobe.drive.ifs.job.RenameHandler$1.call(RenameHandler.java:95)
at com.adobe.drive.ifs.job.RenameHandler$1.call(RenameHandler.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)
Caused by: java.lang.NullPointerException
at com.adobe.drive.connector.cmis.client.CMISProxy.buildQuery(CMISProxy.java:2086)
at com.adobe.drive.connector.cmis.client.CMISProxy.query(CMISProxy.java:1987)
at com.adobe.drive.connector.cmis.client.CMISProxy.getDescendantDocuments(CMISProxy.java:196 1)
at com.adobe.drive.connector.cmis.client.CMISProxy.hasCheckedOutDocumentsByAnyUser(CMISProxy .java:1920)
at com.adobe.drive.connector.cmis.handler.Handler.isCheckedOut(Handler.java:305)
at com.adobe.drive.connector.cmis.handler.MoveHandler.execute(MoveHandler.java:95)
at com.adobe.drive.connector.cmis.handler.MoveHandler.execute(MoveHandler.java:1)
at com.adobe.drive.internal.data.manager.DataManager.execute(DataManager.java:3162)
at com.adobe.drive.internal.data.manager.DataManager.execute(DataManager.java:3114)
at com.adobe.drive.data.manager.call.AbstractFSCall.executeConnector(AbstractFSCall.java:323 )
at com.adobe.drive.data.manager.call.Move.callConnector(Move.java:501)
at com.adobe.drive.data.manager.call.Move.moveRemoteSource(Move.java:302)
at com.adobe.drive.data.manager.call.MoveFinder.moveToEmptyDestination(MoveFinder.java:83)
at com.adobe.drive.data.manager.call.MoveExplorer.moveToEmptyDestination(MoveExplorer.java:7 0)
at com.adobe.drive.data.manager.call.Move.execute(Move.java:142)
at com.adobe.drive.internal.data.manager.DataManager.moveAsset(DataManager.java:3892)
at com.adobe.drive.internal.biz.filesystem.FileSystemService$12.execute(FileSystemService.ja va:998)
at com.adobe.drive.internal.biz.filesystem.FileSystemService$FSRunnable.run(FileSystemServic e.java:1803)
at com.adobe.drive.data.internal.persistence.PersistenceRunner.run(PersistenceRunner.java:11 9)
at com.adobe.drive.internal.biz.filesystem.FileSystemService.run(FileSystemService.java:1666 )
... 7 more
Logs on "New folder" action
2012/09/28 05:23:42,321 [IFSConnection-1] FATAL IFSConnection - NASTY Runtime exception for Request: CREATE
com.adobe.drive.biz.filesystem.FileSystemException: com.adobe.drive.data.model.DriveException: Error creating directory
at com.adobe.drive.internal.biz.filesystem.FileSystemService.wrapException(FileSystemService .java:1623)
at com.adobe.drive.internal.biz.filesystem.FileSystemService.run(FileSystemService.java:1673 )
at com.adobe.drive.internal.biz.filesystem.FileSystemService.create(FileSystemService.java:8 67)
at com.adobe.drive.ifs.job.CreateHandler$1.mkDir(CreateHandler.java:204)
at com.adobe.drive.ifs.job.CreateHandler$1.call(CreateHandler.java:183)
at com.adobe.drive.ifs.job.CreateHandler$1.call(CreateHandler.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)
Caused by: com.adobe.drive.data.model.DriveException: Error creating directory
at com.adobe.drive.internal.data.manager.DataManager.create(DataManager.java:4434)
at com.adobe.drive.internal.biz.filesystem.FileSystemService$10.execute(FileSystemService.ja va:885)
at com.adobe.drive.internal.biz.filesystem.FileSystemService$10.execute(FileSystemService.ja va:1)
at com.adobe.drive.internal.biz.filesystem.FileSystemService$FSCallable.run(FileSystemServic e.java:1767)
at com.adobe.drive.data.internal.persistence.PersistenceRunner.run(PersistenceRunner.java:11 9)
at com.adobe.drive.internal.biz.filesystem.FileSystemService.run(FileSystemService.java:1666 )
... 7 more
There might be something wrong with our implementation as well. But I am not able to figure out where lies the problem.
-
5. Re: Rename, New folder action using Drive CMIS connector
Gang_Z Sep 28, 2012 3:29 AM (in response to mandarpkulkarni@gmail.com)just from the log, it seems our CMIS connector cannot get correct capabilities related to move, create operation from your DAM, please check it you DAM exports those capabilities according to CMIS 1.0 spec
-
6. Re: Rename, New folder action using Drive CMIS connector
mandarpkulkarni@gmail.com Sep 28, 2012 3:33 AM (in response to Gang_Z)Okay, that sounds helpful. I will check the set of CMIS methods we have written so far. Our project is work-in-progress. This has been the main obstacle where we don't know what action from Drive side will invoke which methods on our side.
-
7. Re: Rename, New folder action using Drive CMIS connector
mandarpkulkarni@gmail.com Sep 28, 2012 3:58 AM (in response to Gang_Z)I believe CMIS connector reads the capabilities returned by getRepositoryInfo method, correct? I checked our implementation and the method returns the capabilities consistent with our system's properties. Do you have more information on which specific capability and its value is expected by Drive's CMIS connector?
-
8. Re: Rename, New folder action using Drive CMIS connector
Gang_Z Sep 28, 2012 7:39 PM (in response to mandarpkulkarni@gmail.com)Yes, our CMIS connector reads the capabilities returned by getRespositoryInfo method
few questions here
1) Does your Implementation of CMIS are compliant with RFC4287 and RFC5023?
2) Are the capabilities elements returned with cmis prefix and referred by the namspace http://docs.oasis-open.org/ns/cmis/core/200908/?
3) Is it possible you were testing as an user with limited modifiable rights?
-
9. Re: Rename, New folder action using Drive CMIS connector
mandarpkulkarni@gmail.com Oct 1, 2012 6:25 AM (in response to Gang_Z)To answer your questions:
#1. I believe these are Atom Syndication Format and Atom Publishing Protocol RFCs. Our CMIS implementation is still a work in progress. So some CMIS methods are complete, some are underway. For the methods completed we have tried to be consistent with the sample output shown in CMIS spec. But I am revisting our code to check the compliance with the RFCs you mentioned.
#2. I am checking this.
#3. Which user are you refering to - user of our DAM system which is entered in Drive's (CMIS connector) login window or the Windows user?
-
10. Re: Rename, New folder action using Drive CMIS connector
mandarpkulkarni@gmail.com Oct 10, 2012 8:29 AM (in response to mandarpkulkarni@gmail.com)#1. I have verified compliance with the specified RFCs.
#2. Yes, the capabilities elements are returned with cmis prefix and referred by the required namespace.
#3. I assume you were talking about the user of our system that I use for CMIS connector login. In that case, yes, I have been testing this admin user.
Any other thoughts why I might be facing the problems still?
-
11. Re: Rename, New folder action using Drive CMIS connector
Gang_Z Oct 10, 2012 11:36 PM (in response to mandarpkulkarni@gmail.com)Hi
Currenly, no any idea further. however I'd like to help you on this if you can provide more information, like your connector jar, how to connect to a instance of your server. maybe I can debug it for you
Thanks
-
12. Re: Rename, New folder action using Drive CMIS connector
mandarpkulkarni@gmail.com Oct 10, 2012 11:51 PM (in response to Gang_Z)That sounds great. Much appreciated. Would you like to take the discussion forward here or over email?
Ours is a .NET application. I can provide you the url of CMIS server endpoint and the credentials. What else would you need?
-
13. Re: Rename, New folder action using Drive CMIS connector
Gang_Z Oct 11, 2012 1:18 AM (in response to mandarpkulkarni@gmail.com)let discuss it over email.
Please send me the url of CMIS server endpoint, the credentials and the connector jar, thanks.
I cannot give you an ETA of the invetigation result, I hope I can finish it in two-three days
-
14. Re: Rename, New folder action using Drive CMIS connector
mandarpkulkarni@gmail.com Oct 11, 2012 1:43 AM (in response to Gang_Z)Please let me know the email id on which I am supposed to send the details.
-
15. Re: Rename, New folder action using Drive CMIS connector
Gang_Z Oct 11, 2012 1:50 AM (in response to mandarpkulkarni@gmail.com)sorry, it is gzheng@adobe.com

