Access Document content in Java action : 'virtual' NodeRef ?

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.

fcamblor

Hi all,

I'd like, in a Java action called inside a workflow, to retrieve the document content I just submitted.
I encountered some strange behaviour (to my point of view) : when executing action targetting document(s) : these document(s) seems inside sort of "virtual" NodeRef.
I'd like to know if my assumption (about "virtual" noderef) is true, or, if not, I'd like to understand the underlying behaviour about this

My processdefinition sample :

<process-definition xmlns="urn:jbpm.org:jpdl-3.1" name="wf:adhocCustom">
&nbsp;&nbsp; …
&nbsp;&nbsp; <task-node name="adhoc">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <task name="wf:adhocTask" swimlane="assignee">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <event type="task-create">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <script>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if (bpm_workflowDueDate != void) taskInstance.dueDate = bpm_workflowDueDate;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if (bpm_workflowPriority != void) taskInstance.priority = bpm_workflowPriority;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </script>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </event>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </task>
&nbsp;&nbsp;&nbsp;<transition name="" to="completed">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <action class="foo.bar.MyAction">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </action>
&nbsp;&nbsp;&nbsp; </transition>
&nbsp;&nbsp; </task-node>
&nbsp;&nbsp; …&nbsp;&nbsp; 
</process-definition>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Then I have following implementation :

public class MyAction extends JBPMSpringActionHandler {
   
    private NodeService nodeService;
    private ContentService contentService;
    private FileFolderService fileFolderService;
    

    @Override
    protected void initialiseHandler(BeanFactory factory)
    {
        ServiceRegistry services = (ServiceRegistry) factory.getBean(ServiceRegistry.SERVICE_REGISTRY);
        nodeService = services.getNodeService();
        contentService = services.getContentService();
        fileFolderService = services.getFileFolderService();
    }

    public void execute(final ExecutionContext context) throws Exception
    {
      // Retrieving current "virtual" node hosting modified documents [1]
      NodeRef virtualDirectory = ((JBPMNode) context.getContextInstance().getVariable("bpm_package")).getNodeRef();
      
      // Browsing every modified files, and calling target sites deployments [2]
      for(FileInfo fileInfo : fileFolderService.listFiles(virtualDirectory)){
         // Retrieving document file path & content
         Path filePath = nodeService.getPath(fileInfo.getNodeRef());
         String fileContent = contentService.getReader(fileInfo.getNodeRef(), ContentModel.PROP_CONTENT).getContentString();
         
         // …
      }
    }
}
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

In [1] I retrieve current bpm_package's NodeRef.
In my particular case, as I said earlier, this NodeRef seems to not be an "existing" Node Reference (some sort of "virtual directory).
I made this assumption because :
When I execute fileFolderService.getFileInfo(virtualDirectory), it returns null (directory seems not to *really* exist)When iterating over virtualDirectory children ([2]), I only see modified document (other documents residing at the same level of the current modified document don't appear in the listing)
Are my assumptions right ?
(that is : is the algorithm in [2] a "good" algorithm allowing to retrieve modified document(s) content(s) ?)

Thanks in advance !

mitpatoliya

No ALAIK there is no concept of virtual nodeRef in alfresco.
There might be something else you are missing here.
try to call the same class on some event like "node-leave" event.