cancel
Showing results for 
Search instead for 
Did you mean: 

documentlibrary and documentlibrary-v2 webscripts

alfexp
Champ in-the-making
Champ in-the-making
Hello all,

Alfresco 4.2 has two version of documentlibrary webscripts - documentlibrary and documentlibrary-v2, as a default the v2 version is used (by Share), to use
the documentlibrary version (not v2) we can change "resolver.doclib.doclistDataUrl" bean configuration in slingshot-documentlibrary-context.xml (Share) file - however the json format
returned from documentlibrary version webscripts are not properly handled by Share 4.2 - to make it work I had to modify the structure of json responses.

Am I missing something? Is there a way to configure Alfresco Share 4.2 to use documentlibrary version webscripts without changing json strucutres?


I have to upgrade my extensions from Alfresco 3.4 to Alfresco 4.2, a lot of changes are located in documentlibrary directory. What is the proper way to do this:
a) move the changes from Alfresco 3.4 documentlibrary directory to Alfresco 4.2 documentlibrary directory,
b) move the changes from Alfresco 3.4 documentlibrary directory to Alfresco 4.2 documentlibrary-v2 directory?


Thank you for your help,
Tom
2 REPLIES 2

ddraper
World-Class Innovator
World-Class Innovator
The Document Library has probably seen the most changes in Share… there were large changes between 3.4 and 4.0 and then again from 4.1 to 4.2. The 4.2 WebScript (ending in -v2) combines both the toolbar.get and documentlist.get WebScripts (e.g. it instantiates both the toolbar and documentlist client-side JavaScript widgets). An entirely new WebScript was created so that it would be possible for 3rd party developers to "swap" back the previous regions in the Document Library template and use those old WebScripts.

If you have extensions in 3.4 that you want to move to 4.2 then it is highly likely that you'll want to take advantage of the new extension mechanisms that weren't present in 3.4… presumably you copy/pasted the original 3.4 WebScripts into the web-extension path and made updates there? If that's the case then you should investigate extending the updated WebScripts rather than replacing them.

Regards,
Dave

alfexp
Champ in-the-making
Champ in-the-making
Thank you for the quick response.

My changes are already integrated into 4.2c version of documentlibrary directory - however I had problems to make it work so I tried to switch fresh version of Alfresco from using documentlibrary-v2 to documentlibrary, I thought that it should be easy way to do it -  I made the following steps (using only the original version of Alfresco and Alfresco Share 4.2c - without any custom modifications):

1. I set basePath (resolver.doclib.doclistDataUrl) parameter as "/slingshot/doclib",
2. I changed '/slingshot/doclib2/node/' to '/slingshot/doclib/node/' in share\WEB-INF\classes\alfresco\templates\org\alfresco\import\alfresco-util.js file,

however this was insufficient - I had to change the strucutre of json responses to make it work - I have to test it yet.

Thanks,
Tom
Getting started

Tags


Find what you came for

We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.