AnsweredAssumed Answered

NodeRef change while publishing

Question asked by aussen2 on Apr 16, 2012
Latest reply on Apr 16, 2012 by aussen2
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 case for the "adjusted" Transfer Service that WQS publishing is using (because source and target is the same repository). I found that the nodeRefs for published nodes in WQS only slightly differ from their source nodes' nodeRefs. So I assume that these nodeRefs are somehow created programmatically. Can you explain how exactly this is working?

The reason I am asking is this use case: As Alfresco doesn't support complex data types we are "augmenting" associations between nodes with additional data stored in serialized form in a text field (d:text). We use custom form components to display and update this additional data alongside the associations. They also map the additional data to its corresponding associated node. So if we for example have an article node that has two image nodes (workspace://SpacesStore/d6e441a7-a4e1-4c21-96bf-20583aa9e5d1 and workspace://SpacesStore/e9f552b8-b5f2-5d32-07cg-31694bb0f6e2) associated, the content of the text field with the additional data might look something like this:


Now this mapping breaks when the nodeRef changes while publishing. Thus, I was wondering if there is at least some part of the nodeRef that is persistent. That seems to be the case for the published nodes that we observed. But in order to count on this we would need to understand the mechanism behind the nodeRef creation process in this special case.