Mailing-List: contact dev-help@chemistry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@chemistry.apache.org
Received-SPF: pass (nike.apache.org: domain of fguillaume@nuxeo.com designates
 209.85.212.180 as permitted sender)
MIME-Version: 1.0
Date: Wed, 12 Mar 2014 19:53:27 +0100
Message-ID: 
 <CAF-4BpO+Xsg1JisP5wA3=1qUEV-W8ouQOoDjudLFnW3kzU9-RA@mail.gmail.com>
Subject: folder with non-accessible parent (AtomPub)
From: Florent Guillaume <fg@nuxeo.com>
To: List-Chemistry <dev@chemistry.apache.org>
Content-Type: text/plain; charset=UTF-8

Hi,

In some of our applications a given folder (a user's workspace) has
internally a parent that exists but is not accessible to the
particular user. Therefore we return no parent for it.

However Chemistry assumes that only the root can have no parent:
org.apache.chemistry.opencmis.client.runtime.FolderImpl.getParents
checks if it's not the root, and if not calls
org.apache.chemistry.opencmis.client.bindings.spi.atompub.NavigationServiceImpl.getFolderParent
which fails as there's not rel="up" link.

What do you think? Is what we do illegal according to the spec, or is
it just Chemistry that has to be patched?

Florent

-- 
Florent Guillaume, Director of R&D, Nuxeo
Open Source Content Management Platform for Business Apps
http://www.nuxeo.com   http://community.nuxeo.com