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 5.0.x, 5.1.x, webscript 'cmis' not defined

dhartford

There seems to be an issue with webscripts that rely in CMIS binding.

ReferenceError: "cmis" is not defined

The same webscripts work in alfresco 4.2.f, so has something changed?

   var cmisConnection = cmis.getConnection();
   var cmisSession = cmisConnection.getSession();
….
‍‍‍‍‍

other forum references:
https://forums.alfresco.com/forum/developer-discussions/web-scripts/web-script-cmis-query-12152011-0923
http://forums.alfresco.com/forum/developer-discussions/other-apis/alfresco-50-webscript-cmis-not-defined-02262015-1029

Find more posts tagged with

Comments

dhartford

Apparently there is an open ticket around this issue, but no momentum:

https://issues.alfresco.com/jira/browse/MNT-12795

mrogers

Yes its still an issue that's been jammed for too long.

dhartford

I've voted for this ticket, but not able to add comments.

We chose to build alfreso-specific dashlets, using the CMIS behind the server-side webscripts as it handled security. This provided some convenience and performance, but was a conscious decision to lock-in to Alfresco itself.

Now, we have some concerns - would it have been preferred to create a liferay portlet or regular webapp talking over CMIS rather than embed into Alfresco with their dashlet and webscript approach (as this CMIS-no-longer-available-serverside-webscript bug has been lingering for a while)?

dhartford

Is there any feedback from Alfresco if this will be a 'not fix' kind of issue, or if there are actual plans to fix it?

dhartford

created a community ticket (versus the customer MNT ticket) - https://issues.alfresco.com/jira/browse/ALF-21434

dhartford

The above community ticket was closed related to duplicate of MNT, was hoping for visibility in the 5.1.x community stream (this has been open issue since 4.2.f).

dhartford

Tested 5.1.c (201510) release of Alfresco.

Still unable to add comments to: https://issues.alfresco.com/jira/browse/MNT-12795

Using Jeff Potts example (https://forums.alfresco.com/forum/developer-discussions/web-scripts/web-script-cmis-query-12152011-0923), still get this error with 5.1.c/201510 EA release, nor the example attached directly to MNT-12795 as it also gets the same error:

ReferenceError: \"cmis\" is not defined.‍

This is a regression issue as this used to work with older versions of alfresco (last that worked was Alf 4.2.f). Usecase is when you want to run CMIS queries *through* webscript (such as an alfresco dashlet).

resplin

Your persistence on this issue has kept visibility on it. It is one of those issues that hasn't been big enough to make a priority, but is too big to fix quickly. There was some internal conversation on the issue that I opened up in the issue tracker.

A few notes on the issue tracker:
* MNT is the project where we prioritize customer fixes that are likely to end up in a hot fix or service pack.
* Because MNT largely consists of customer raised issues, it defaults to private settings so we don't accidentally leak customer information. Unfortunately, we often forget to make things public when there is no customer info.
* The public used to be able to comment on MNT issues. I'm not sure what changed, but it was accidental. We will get it fixed.

This is unlikely to be fixed in time for the 5.1 release, but it hasn't been forgotten. Sorry about the delay.

dhartford

Here is some key api calls that I'm using:

var cmisConnection = cmis.getConnection();
var cmisSession = cmisConnection.getSession();
cmisSession.getTypeDefinition(…).getPropertyDefinitions()
var quickOperationContext = cmisSession.createOperationContext();
quickOperationContext.setMaxItemsPerPage(100);
quickOperationContext.setIncludeAllowableActions(false);
var results = cmisSession.query(selectQuery , false, quickOperationContext).skipTo(nextIndex).getPage(model.pageSize).iterator();

They are all standard / traditional chemistry API calls using the old CMIS integration approach. Would hate to have to rewrite them all into something that isn't as portable (i.e. I just change 'var' with the actual object when using codesnippet/logic to/from systems other than Alfresco's webscripts, making it really easy to go back and forth and reuse the same skillset…minus the authentication management that is built in to webscripts).

EDIT: as an additional option, if there is a good example of setting up a java-backed data webscript w/ opencmis where still have the .get.json.ftl / .get.desc.xml referencing the java class approach, that may be an alternative approach..I haven't done such a thing.
-Darren

resplin

After researching the issue a couple of times over the past two years, I was asked to make a final decision on it. I decided against fixing the problem. You can read my reasoning here:

https://issues.alfresco.com/jira/browse/MNT-12795?focusedCommentId=543254