Skip navigation
Currently Being Moderated

Developing: Endless loop in Adobe Bridge with and Adobe Drive CMIS Connector

May 10, 2013 1:27 AM

Tags: #cs6 #cmis #developing #adobe_bride_cs6 #adobe_drive

Hi

 

Currently I’m implementing a CMIS-Server for the dam system of my company, using the apache chemistry framework. One of the main requirements is that adobe drive works with it.

 

At the moment I implemented only the navigation services (getChildren, getObject, …) and the repository services and test them against adobe drive. It’s already possible to navigate through folders and read assets with ad4 and the finder. So 3 days ago I installed adobe bridge (CS6) and test my server again.

 

My test environment is very easy.

root(1 object)->test1(0 objects; empty)

 

First I’m opening my repository with adobe drive and then I switch to bridge and connect it. Bridge shows me the folder test1 with no errors. So I double-click it and now bridge is in an endless loop. The notification switch between ‘Keine anzuzeigenden Elemente’(No elements to show) and ‘Einen Moment bitte, die Suche läuft …’(Searching, please wait …). This only happens in bridge. When I open the folder with the finder it just works, without the loop.

 

So I logged all requests, which were send by adobe drive, and get this list.

 

Connecting with adobe drive


getRepositoryInfos

getTypeChildren (null) -> all basetypes

getTypeDecendants (cmis:document)

getTypeChildren (null) -> all basetypes (Why two times?)

getTypeDecendants (cmis:document) (Why two times?)

getRepositoryInfos (Why two times?)

getObjectByPath (/.hidden)

getObjectByPath (/.hidden)

getObjectByPath (/.hidden) (Why so often?)

getObjectByPath (/DCIM)

getObjectByPath (/mach_kernel)

getObjectByPath (/.Spotlight-V100)

getObjectByPath (/.metadata_never_index)

getObjectByPath (/.metadata_never_index_unless_rootfs)

getObjectByPath (/.metadata_never_index)

getObjectByPath (/mach_kernel)

getObjectByPath (/.metadata_never_index_unless_rootfs)

getChildren (cmis:folder,0) (rootfolder) returning only one element (test1)

getObjectParents(cmis:folder,127) (test1) returning the rootfolder

getObjectByPath (/.hidden)

getObjectByPath (/mach_kernel) …

 

Open the Cmis repository in bridge and doubleclick the repository

 

getChildren (cmis:folder,0) (rootfolder) returning only one element (test1)

getObjectParents(cmis:folder,127) (test1) returning the rootfolder

 

Then I double click the test1 folder

 

getObject(cmis:folder,127)(test1)

getChildren(cmis:folder,127) -> empty list

… (endless loop)

 

 

I already checked getObject and getChildren against a reference implementation (FileShare Repository of apache Chemistry) and it returns exactly the same structure. Only the name and the timestamps are different. So my second though was to check the repository capabilities and as well they are both equal. Now I’m a little bit desperate because I spend already 3 days in try and error bugfixing but nothing worked. So here are my questions.

 

  1. Is there a logfile for bridge because I thing this refreshing happens after an exception. I already checked the adobe drive log and it contains only asset not found errors for (e.g mach_kernel …).
  2. In which circumstances does bridge reloads a folder?
  3. Debugging of adobe drive: I already read http://forums.adobe.com/message/3928595 but it doesn’t work in AD4 any more, I only get info/error/fatal messages.(I changed the log4j config files in AD4ServiceManager.) Does something changed or did I forget something?
  4. Why does AD4 make 2 or more times the exact same request? (Look table above).

 

 

I hope my English is good enough to understand.

 

Thanks

 
Replies

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points