You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chemistry.apache.org by "Florian Müller (JIRA)" <ji...@apache.org> on 2013/03/14 13:52:12 UTC

[jira] [Resolved] (CMIS-638) getContentChanges returns no for a deleted object

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

Florian Müller resolved CMIS-638.
---------------------------------

       Resolution: Fixed
    Fix Version/s: OpenCMIS 0.9.0

Thanks for the hint!
                
> getContentChanges returns no <atom:link rel="self"> for a deleted object
> ------------------------------------------------------------------------
>
>                 Key: CMIS-638
>                 URL: https://issues.apache.org/jira/browse/CMIS-638
>             Project: Chemistry
>          Issue Type: Bug
>          Components: opencmis-commons
>    Affects Versions: OpenCMIS 0.5.0
>            Reporter: linzhixing
>            Assignee: Florian Müller
>             Fix For: OpenCMIS 0.9.0
>
>
> CMIS specification 3.5.1(Feeds) says that any Atom feed should include an atom link with relation "self".
> http://docs.oasis-open.org/cmis/CMIS/v1.1/cs01/CMIS-v1.1-cs01.html
> AtomPubUtils#writeContentChangesObjectEntry method makes a change log feed but seems not to write some atom link containing "self" for objects deleted from the repository. When I use a "self" link to convert an atom collection to a client framework(ActiveCMIS, Ruby), it fails.
> I traced the Chemistry code and found:
> -writeContentChangesObjectEntry firstly initializes an objectInfo instance.
> -AbstractCmisService#getObjectInfo tries to make an objectInfo referring to the objectData in the repository.
> -But objectData for deleted objects are already lost from the repository, of course, and objectInfo is returned as null.
> -If objectInfo is null, writeContentChangesObjectEntry ends returning null as well. The following writeSelfLink methods and such thing are all skipped.
> I investigated the above on opencmis-server-bindings-0.5.0 but it is still the case on the latest 0.9.0-beta.
> Is is to be considered a bug of OpenCMIS implementation or am I wrong in the interpretation of CMIS specification?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira