Mailing-List: contact chemistry-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: chemistry-dev@incubator.apache.org
Message-ID: <1010065060.8721265063480290.JavaMail.jira@brutus.apache.org>
Date: Mon, 1 Feb 2010 22:31:20 +0000 (UTC)
From: "Chris Hubick (JIRA)" <jira@apache.org>
To: chemistry-dev@incubator.apache.org
Subject: [jira] Updated: (CMIS-108) APPObject access to APPObjectEntry
In-Reply-To: <1801172333.8691265063480271.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CMIS-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Hubick updated CMIS-108:
------------------------------

    Attachment: chemistry_appobject_entry.patch

> APPObject access to APPObjectEntry
> ----------------------------------
>
>                 Key: CMIS-108
>                 URL: https://issues.apache.org/jira/browse/CMIS-108
>             Project: Chemistry
>          Issue Type: Bug
>          Components: atompub
>            Reporter: Chris Hubick
>         Attachments: chemistry_appobject_entry.patch
>
>
> Hi.
> When dealing with a Repository via APPContentManager, the vast majority of my code is happy working with the higher level CMISObject derived interfaces (Document/Folder).  But there are a few select places where I require access to some underlying low-level information, such as the remote content href URL for a Document ( APPObjectEntry.getContentHref() ).  Coding the whole project using the low-level API's is quite burdensome, and if I have an APPObject reference, I would rather just have the ability to get a reference to it's underlying APPObjectEntry.
> Thanks.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.