topic Re: API differences Javascript vs JAVA in Alfresco Archive

API differences Javascript vs JAVA

darkredd — Wed, 05 Aug 2015 09:33:02 GMT

Hello everyone,A silly question perhaps, however here goes: I am trying to leverage an already existing custom action which creates document links.I have a slight lack of understanding of API differences. In Javascript I am able to use the custom action's logic to create link with a script (Action R

Re: API differences Javascript vs JAVA

mrogers — Wed, 05 Aug 2015 10:09:00 GMT

IIRC I don't think you can have properties on an association. Well except the name and type which are special cases. linkParams are actually properties for the new node.

I suspect your LINK_URI is not correct. There is a convention to follow that is enforced by the file folder service.

Re: API differences Javascript vs JAVA

darkredd — Wed, 05 Aug 2015 10:54:00 GMT

Hi mrogers,

Thanks for your response. However my "LINK_URI" is correct because it's a copy and paste of the uri which I use in javascript. On the original post {custom.uri} is a replacement of the actual uri which in fact is assigned to LINK_URI. Based on your response I would think I am then uri the NodeService.create() method in a wrong, specifically when it come the association part.
What would you suggest I look at to achieve this?

Re: API differences Javascript vs JAVA

darkredd — Wed, 05 Aug 2015 13:09:00 GMT

Hi,

I managed to find a solution to my problem. As suspected it was lack of understanding of the API. I had placed my arguments in the wrong order as expected by the method, and one QName ("ContentModel.TYPE_CONTENT") was wrong. In the end I had to change the method to look like this:
This is the new order:

nodeService.createNode(parentDest, ContentModel.ASSOC_CONTAINS, ContentModel.TYPE_LINK, QName.createQName(LINK_URI), linkParams)‍

The one with an error was:

nodeService.createNode(parentDest, ContentModel.ASSOC_CONTAINS, QName.createQName(LINK_URI), ContentModel.TYPE_CONTENT, linkParams)‍

Now I am able to achieve what I had set out to do.
Thank you.