NodeRef change while publishing

aussen2 — Mon, 16 Apr 2012 15:42:20 GMT

Could you please explain how you handle the nodeRef mapping when publishing assets in WQS? My understanding is that normally the Transfer Service will make sure that a transferred node gets the same nodeRef in the target repository that is has in the source repository. Obviously that cannot be the c

Re: NodeRef change while publishing

aussen2 — Mon, 16 Apr 2012 18:05:07 GMT

Okay, I found the logic that I was looking for in org.alfresco.module.org_alfresco_module_wcmquickstart.publish.NodeRefMapper:


public NodeRef mapSourceNodeRef(NodeRef node)
    {
        StringBuilder nodeId = new StringBuilder(node.getId());
        if (nodeId.length() == 36)
        {
            for (int index = 35; index >= 0; –index)
            {
                int srcChar = nodeId.charAt(index);
                if (srcChar == '-')
                {
                    continue;
                }
                int destChar = srcCharToDestChar(srcChar);
                if (destChar != srcChar)
                {
                    nodeId.setCharAt(index, (char)destChar);
                    break;
                }
            }
        }
        else
        {
            nodeId.append('f');
        }
        return new NodeRef(node.getStoreRef(), nodeId.toString());
    }
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

As the change logic for the nodeRef string starts at the last character and stops once a character was successfully substituted I assume it is save to use the first 20 characters of the nodeRef for our use case. These should go unchanged when publishing nodes in WQS as well as between two repositories in more than 99% of all cases.

topic Re: NodeRef change while publishing in Alfresco Archive

NodeRef change while publishing

Re: NodeRef change while publishing