chemistry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jennifer Deigendesch (JIRA)" <>
Subject [jira] [Resolved] (CMIS-951) Problem with applying policy
Date Fri, 02 Oct 2015 08:58:27 GMT


Jennifer Deigendesch resolved CMIS-951.
    Resolution: Fixed

We found the problem... The bug where the object id will be used instead of the policy id
was wrong fixed. I changed the wrong variable. The variable must be changed from "objectId"
into "policyId" within method "CreateIdObject(..)".

> Problem with applying policy
> ----------------------------
>                 Key: CMIS-951
>                 URL:
>             Project: Chemistry
>          Issue Type: Bug
>          Components: dotcmis
>    Affects Versions: DotCMIS 0.7
>         Environment: AtomPub
> CMIS for .NET
> C#
>            Reporter: Jennifer Deigendesch
>            Assignee: Florian Müller
>         Attachments: 00054-request (object).log, 00054-response (object).log, 00058-request
(policy).log, 00058-response (policy).log, AnswerMailinglist.msg, object.xml, policy.xml
> Hi altogether,
> I’m using DotCMIS 0.7 for .NET via AtomPub and I have a problem with applying a policy
to a document.
> First I already fixed the bug in PolicyService in method “ApplyPolicy” to load the
link for the given policyId and not for the objectId. But I’ll get the exception “Operation
not supported by the repository for this object”...
> I also find out, that the link relation of policies is not available in the binding cache.
Instead the link relation of allowable actions is available..
> I already tried to create and apply a policy via the CMIS Workbench (where the bug in
method "AppylPolicy" is already fixed) and it works.
> I've already written a mail to the mailing list. The answer is attached as well as the
logs of the traffic between client and server (and the XML files of the created object and
policy). There you can see that the server sends the policy link.
> I'm really happy to get help soon :)

This message was sent by Atlassian JIRA

View raw message