[ACE-2346] CLONE - Web Script - Status 500 error on 'Edit Properties' page after adding 'Restrictable' aspect through CMIS 1.1 API Created: 30-Jul-14  Updated: 21-Nov-14  Resolved: 08-Aug-14

Status: Closed
Project: Alfresco One Platform
Component/s: CMIS, Document Library
Affects Version/s: 5.0
Fix Version/s: 5.0

Type: Bug Priority: Blocker
Reporter: Alfresco QA Team (Inactive) Assignee: Closed Issues
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0 minutes
Time Spent: 2 hours
Original Estimate: Not Specified

Alfresco Enterprise v4.2.0 (r57217-b28) schema 6034, RHEL 6.4x64, Oracle 11g R2 (, Tomcat 7.0.42, Client: IE8, Windows 7 X64

Issue Links:
is clone of MNT-10226 Web Script - Status 500 error on 'Edi... Closed
Build Location: ftp://pbld01.alfresco.com/nightlybuilds/Enterprise%204.2/4.2.4/build-00474/
Build Number: http://nightlybuilds.alfresco.com/Enterprise-5.0/build-00072/
Testcase ID:



1. Any document and folder are created in Alfresco Share;
2. Chemistry-opencmis-workbench-0.10.0 (or higher) is launched;
3. Connect to repository using Browser binding (http://localhost:8080/alfresco/api/-default-/public/cmis/versions/1.1/browser)
4. Locate the document and open Property Editor;
5. In the Secondary Object Type Ids section select Update value, click '+' button and into appeared field enter 'P:dp:restrictable'.
Click Update button; -> the properties are updated
6. Browse to Share, open document details -> Edit properties page

Actual result: Web Script - Status 500 error is displayed on the page (please, verify the attached screenshot)

Note: the same behaviour is for folder - > after adding Restrictable aspect through CMIS 1.1 API Web Script status 500 is displayed on Edit Properties page


Comment by Samuel Langlois [X] (Inactive) [ 30-Jul-14 ]

This needs fixing (and testing!) again on 5.0.
The fix that was made in V4.2-BUG-FIX in r76534 cannot be applied there: the class org.alfresco.repo.domain.PropertyValue is now gone, as part of the removal of AVM.

There are currenttly 3 failing tests in WorkflowFormProcessorTest because of that (see MyAlfresco build #531)


Comment by Samuel Langlois [X] (Inactive) [ 30-Jul-14 ]

Note that in r78626, I removed the modification that was done to WorkflowFormProcessorTest, so that this test does not fail any more.
It will need to be changed back as part of the fix.

Comment by Alan Davis [ 30-Jul-14 ]

Change priority to Blocker as we need to ensure that issues fixed in a service pack are merged forwards to the next major/minor release.

In r78626 HEAD-BUG-FIX Samuel has removed the changes made in the merge from V4.2-BUG-FIX r78498 in order to get the build green again. Merge info was not changed so there is no prompt other than the existence of this issue to indicate that we don't have a 4.2 fix in 5.0.

Comment by Samuel Langlois [X] (Inactive) [ 01-Aug-14 ]

I don't know much about CMIS, frankly!
But this looks good to me, and thank you for reverting the corresponding test as well.
Please merge.

Generated at Thu Jul 09 09:53:21 BST 2020 using JIRA 7.6.3#76005-sha1:8a4e38d34af948780dbf52044e7aafb13a7cae58.