3 Replies Latest reply: May 19, 2011 1:59 AM by mandarpkulkarni@gmail.com RSS

    CMIS connector error

    mandarpkulkarni@gmail.com Community Member

      We are in process of making our product CMIS compliant. Certain CMIS methods have been written on server side and we are testing those against Drive's CMIS connector. Our DAM system is getting mounted as a network drive and I can see all the top level folders alright. But when I try to go into a folder containing documents/files, it doesn't get opened and Drive throws following error in logs. The folders that have only folders inside are getting opened without any error. The log message is not very descriptive. The "assetId" it talks about isn't a parameter in our code. The error is thrown when getChildren method is invoked and when at least one child is a document.

       

      Any ideas on how to troubleshoot this are appreciated. Thanks.

       

      [IFSConnection-4] FATAL IFSConnection - NASTY Runtime exception for Request: QUERY_DIRECTORY
      com.adobe.drive.biz.filesystem.FileSystemException: java.lang.IllegalArgumentException: Illegal value (null): assetId
          at com.adobe.drive.internal.biz.filesystem.FileSystemService.run(FileSystemService.java:1673 )
          at com.adobe.drive.internal.biz.filesystem.FileSystemService.dir(FileSystemService.java:368)
          at com.adobe.drive.ifs.job.QueryDirectoryHandler$1.init(QueryDirectoryHandler.java:122)
          at com.adobe.drive.ifs.job.QueryDirectoryHandler$1.call(QueryDirectoryHandler.java:86)
          at com.adobe.drive.ifs.job.QueryDirectoryHandler$1.call(QueryDirectoryHandler.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.IllegalArgumentException: Illegal value (null): assetId
          at com.adobe.drive.connector.api.CallContract.checkNotNull(CallContract.java:42)
          at com.adobe.drive.connector.api.recipe.RemoteResponse.createFileUpdateRecipe(RemoteResponse .java:126)
          at com.adobe.drive.connector.cmis.helper.UpdateRecipeHelper.refreshFileData(UpdateRecipeHelp er.java:171)
          at com.adobe.drive.connector.cmis.helper.UpdateRecipeHelper.createUpdateRecipe(UpdateRecipeH elper.java:113)
          at com.adobe.drive.connector.cmis.handler.GetChildrenHandler.execute(GetChildrenHandler.java :127)
          at com.adobe.drive.connector.cmis.handler.GetChildrenHandler.execute(GetChildrenHandler.java :1)
          at com.adobe.drive.model.internal.synchronization.AssetSynchronizer.execute(AssetSynchronize r.java:429)
          at com.adobe.drive.model.internal.synchronization.AssetSynchronizer.synchronizeStructure(Ass etSynchronizer.java:349)
          at com.adobe.drive.internal.data.manager.DataManager.getChildren(DataManager.java:1672)
          at com.adobe.drive.internal.biz.filesystem.FileSystemService$2.execute(FileSystemService.jav a:297)
          at com.adobe.drive.internal.biz.filesystem.FileSystemService$2.execute(FileSystemService.jav a:1)
          at com.adobe.drive.internal.biz.filesystem.FileSystemService$FSCallable.run(FileSystemServic e.java:1760)
          at com.adobe.drive.data.internal.persistence.PersistenceRunner.run(PersistenceRunner.java:11 9)
          at com.adobe.drive.internal.biz.filesystem.FileSystemService.run(FileSystemService.java:1659 )