Well this is turning out to be much harder than it seemed, even just passing in a skeleton and manipulating it is presenting various challenges. Here’s what I’m trying to do, though.
My Java service communicates with a legacy process to send it input parameters and receive its output. I can’t do this in Flow because I have to connect to the legacy process on a socket and send it data in XDR format (essentially 4-byte packets). The output is then read off the socket and used to build a response document, which should be in the pipeline when the service completes.
Now I could:
- Build each node in the document manually and then insert the structure in the pipeline - I was trying to avoid this, however.
- Create each response node independently and return them all as separate pipeline variables. Then I could use flow to map them all into the response document.
It seems that neither of these should be necessary, since (IMO) the Java API should expose all the functionality available in the GUI in some shape or form. So I thought I should be able to create a template document based on my pre-defined document type and navigate/manipulate it as necessary. For the time being, it looks like I’m going to revert back to option 1).