CMIS AtomPub Binding Timing Out

Hey, all. Does anybody have trouble with using the Atom feeds in the CMIS implementation where sometimes a list of children will time out? I have:

http://<host>:<port>/emc-cmis-ea/resources/repositories/<docbase>/objects/<object_id>/children

This will sometimes think for a while and then time out. I refresh and it gives me the proper list. The vitals are:

Windows Server 2003

Apache Tomcat 6.0.18

JDK 1.6.0_17

CMIS EA4 release

While I'm at this, is there a way of paring down the amount of stuff in the atom feed? In Documentum's RESTful web services (which I am starting to pine for), I could control which properties were returned, which improved performance in many cases and prevented these potentially long waits while the content server tried to cobble together a list of renditions that I don't need to populate a table view in my iPhone app.

Any help would be appreciated!

Dave

Find more posts tagged with

Comments

jradebaugh

I believe I'm having the same issue. When I execute the call to get the children at the root of my repository it just hangs....I'm currently running a test to see if it ever comes back.

Regarding your second question, there's a way to pass a context filter when you are asking for renditions. See this blog post (it is using Alfresco, but the principle should be the same. http://blogs.alfresco.com/wp/cmis/2010/05/17/alfrescos-interpretation-of-cmis-renditions/

david.matheson

That's really helpful, Jon. Thank you! Using objects/root/children?filter=cmis:objectId I can get back a list of entries with nothing but object IDs in the cmisra:object entry. That's great. I found with Documentum's RESTful web services I would get hanging when it would try to give me back permission information, as well as rendition information. Shutting these off would avoid those situations. Often I just want a list of children object IDs with names and little else.

Let me know if you figure out why things are hanging for you.

jradebaugh

Glad to help! I helped myself in the process -- using filters turned out to solve my performance problem too...though I'm not sure this isn't still a defect on some level.