Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 6B0F3200CAD for ; Wed, 28 Jun 2017 09:44:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 69B74160BE8; Wed, 28 Jun 2017 07:44:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B3CC1160BF7 for ; Wed, 28 Jun 2017 09:44:03 +0200 (CEST) Received: (qmail 48279 invoked by uid 500); 28 Jun 2017 07:44:02 -0000 Mailing-List: contact dev-help@chemistry.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@chemistry.apache.org Delivered-To: mailing list dev@chemistry.apache.org Received: (qmail 48258 invoked by uid 99); 28 Jun 2017 07:44:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Jun 2017 07:44:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id CC095181944 for ; Wed, 28 Jun 2017 07:44:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id Mc1l4sBLerCU for ; Wed, 28 Jun 2017 07:44:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id E040F5FDE4 for ; Wed, 28 Jun 2017 07:44:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 77D5CE0732 for ; Wed, 28 Jun 2017 07:44:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 06C222415D for ; Wed, 28 Jun 2017 07:44:00 +0000 (UTC) Date: Wed, 28 Jun 2017 07:44:00 +0000 (UTC) From: "Edward Wolthuis (JIRA)" To: dev@chemistry.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CMIS-1036) As a Developer I want to be able to use a CMIS selector (or not) when retrieving Objects MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 28 Jun 2017 07:44:04 -0000 Edward Wolthuis created CMIS-1036: ------------------------------------- Summary: As a Developer I want to be able to use a CMIS selector (or not) when retrieving Objects Key: CMIS-1036 URL: https://issues.apache.org/jira/browse/CMIS-1036 Project: Chemistry Issue Type: Improvement Components: opencmis-client-bindings Affects Versions: OpenCMIS 1.1.0 Reporter: Edward Wolthuis When retrieving a Folder via plain HTTP, without using a cmisselector parameter (i.e. GET http://example.com/cmis/repository/123/myFolder), the Specs define that a value of 'children' will be used to return the result. (see section 5.4 at http://docs.oasis-open.org/cmis/CMIS/v1.1/errata01/os/CMIS-v1.1-errata01-os-complete.html#x1-5580004) When using the browser bindings, object retrieval by using the path (i.e. /123/MyFolder) always seems to use a cmisselector parameter with the value of 'object', making it impossible to reproduce the result above. (actually, all Object finders) (see org.apache.chemistry.opencmis.client.bindings.spi.browser.ObjectServiceImpl) Why not let the user decide to use a cmisselector (for example in the Operation Context), or not? -- This message was sent by Atlassian JIRA (v6.4.14#64029)