nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Alfresco CMIS 1.1 compliant?

mangar

I am getting some pushback at work for using the alfresco-opencmis-extension to get aspects to work, specifically "cm:titled"

My question is "Is Alfresco CMIS 1.1 compliant or not?"

I am using 4.2.d community, and OpenCMIS 0.10. Both the Alfresco documentation and the Apache site say they are 1.1 compliant, so why do I have to use the alfresco-opencmis-extension? How long will I have to use it before a standard 1.1 client (like apache chemistry) will work?

Find more posts tagged with

Comments

jpotts

Yes, it is CMIS 1.1 compliant but you have to use the appropriate CMIS URLs:

http://localhost:8080/alfresco/api/-default-/public/cmis/versions/1.0/atom
http://localhost:8080/alfresco/api/-default-/public/cmis/versions/1.1/atom

Note that in 4.2.d I found some problems with secondary type (aspect) support. If you need to work with aspects you may want to upgrade to 4.2.e.

You can read more about CMIS 1.1 and 4.2.d at my blog post <a href="http://ecmarchitect.com/archives/2013/09/15/3554">here</a>.

Jeff

heisenberg

org.alfresco.cmis.CMISServices.getCMISVersion() returns String "1.0" in Alfresco 4.2.e CE. Typo then?

jpotts

Based on the Spring bean config for CMISService which references the CMISServicesImpl class, it sets the version to 1.0.

But when you use OpenCMIS, you can specify which server endpoint to use. And in Alfresco 4.2.e there are two for AtomPub. One is 1.0 and one is 1.1.

If you run this groovy script in the OpenCMIS Workbench:
println session.repositoryInfo.productName
println session.repositoryInfo.productVersion
println session.repositoryInfo.cmisVersion

When you connect to the 1.1 URL, you will get:
Alfresco Community
4.2.0 (r56674-b4848)
CMIS_1_1

When you connect to the 1.0 URL, you will get:
Alfresco Community
4.2.0 (r56674-b4848)
CMIS_1_0

So the answer to your question is, yes, 4.2.e is compliant with CMIS 1.1.

I'm curious as to why you are using that class instead of OpenCMIS?

Jeff

mangar

So I took your advice and switched from my old URL, (alfresco/cmisatom) And used the new ones. I really like not having to use a repository ID that I have to go look up every time I re-install alfresco. (I do that alot)

But the aspects are killing me. When I use the 1.0 URL adding a directory via CMIS with properties like this:

<java>
Map<String, String> props = new HashMap<String, String>();
props.put(PropertyIds.OBJECT_TYPE_ID, "cmis:folder,P:cm:titled");
</java>

It works fine, but with the 1.1 url, it fails.

Is there a different way of doing it for 1.1?

jpotts

Yes, when using CMIS 1.1, first, make sure you are not using the OpenCMIS Extension. You should be dealing with Document and Folder objects not AlfrescoDocument and AlfrescoFolder objects.

Next, you will not use the old extension-based syntax for adding an aspect. Instead, you'll modify the multi-value secondary types property. Here's an example:

public void addAspect(Document doc) {
   List<Object> aspects = doc.getProperty("cmis:secondaryObjectTypeIds").getValues();
   if (!aspects.contains("P:cm:geographic")) {
      aspects.add("P:cm:geographic");
      HashMap<String, Object> props = new HashMap<String, Object>();
      props.put("cmis:secondaryObjectTypeIds", aspects);
      doc.updateProperties(props);
      System.out.println("Added aspect");
   } else {
           System.out.println("Doc already had aspect");
   }

   HashMap<String, Object> props = new HashMap<String, Object>();
   props.put("cm:latitude", 52.513871);
   props.put("cm:longitude", 13.391106);      
   doc.updateProperties(props);
      
   System.out.println("Latitude: " + doc.getProperty("cm:latitude").getValueAsString());
   System.out.println("Longitude: " + doc.getProperty("cm:longitude").getValueAsString());

}
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Jeff

mangar

You are a god. Thank you so much!

mundi

I know the discussion is older, but the mentioned method is not working for me. I have the code:

<java>
Document document = (Document)getAlfrescoFacade().getObjectById("workspace://SpacesStore/e7af5c7c-226a-474d-abee-371bbb33eadb");
List<Object> aspects = document.getProperty("cmis:secondaryObjectTypeIds").getValues();
aspects.add("P:sigi:document");
HashMap<String, Object> properties = new HashMap<String, Object>();
properties.put("cmis:secondaryObjectTypeIds", aspects);
document.updateProperties(properties);

aspects = document.getProperty("cmis:secondaryObjectTypeIds").getValues();
for (Object object: aspects)
System.out.println(object);
</java>

but it does not add the aspect sigi:document. After exucting the code the aspects are still the same as before.
My version is Alfresco Enterprise 4.2.3.

jpotts

Can you verify which service URL you are using?

Jeff

mundi

I'm using the parameter (test server):
<blockcode>
parameters.put(SessionParameter.ATOMPUB_URL, "http://alfresco03.pch.etat.lu:8080/alfresco/api/-default-/public/cmis/versions/1.1/atom");
</blockcode>

jpotts

Make sure you are NOT using the AlfrescoObjectFactoryImpl for your Object Factory Class. That should only be used when you are using the OpenCMIS Extension. Because you are using 1.1 you do not need that extension and it will prevent the aspect from being added.

I just ran this code on 4.2.f CE and it added the aspect successfully:

Session cmisSession = getCmisSession();
   
Folder folder = (Folder) cmisSession.getObjectByPath("/test");
         
HashMap<String, Object> props = new HashMap<String,Object>();

props.put("cmis:name", "testjtp.txt");
         
Document document = createDocument(folder, getLocalFile(), getLocalFileType());
         
List<Object> aspects = document.getPropertyValue("cmis:secondaryObjectTypeIds");

aspects.add("P:sc:productRelated");
         
props = new HashMap<String, Object>();
         
props.put("cmis:secondaryObjectTypeIds", aspects);
         
document.updateProperties(props, true);
         
aspects = document.getPropertyValue("cmis:secondaryObjectTypeIds");
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Jeff

mundi

I used the AlfrescoObjectFactoryImpl so that was the problem…
Thank you very much!

s00pa

Hi, I know this thread is from a while back but I felt that this question was best asked here.

I am finding that using the CMIS 1.1 path when accessing via OpenCMIS, if I copy a document, it doesn't seem to be indexed..
Basically I have a custom object type which has custom properties. I can search using these properties normally but any document copied using CMIS 1.1 doesn't appear in the search results. Also, CMIS query on a property field shows nothing.
However, if I change to the CMIS 1.0 path and perform the copy, then this all works. Seems like a bug to me but would be interested to see if this is replicated for others or if there is a workaround. I really don't want to have to go back to CMIS 1.0 because I rather like the newer aspect support in 1.1 but this is a major game-changer.

using Apache OpenCMIS 0.12
Running alfresco 5.0.c
using the following paths:
1.0 : alfresco/api/-default-/public/cmis/versions/1.0/atom
1.1 : alfresco/api/-default-/public/cmis/versions/1.1/atom

–
Sean