Hey Mike, I don't have an answer to your question, but I wanted to ask about your use case to better understand your question.
Do you intend to pass metadata from one completed workflow into the next? Or are you looking at different levels (i.e. Tasks, Events, etc..) Can you provide a simple example so we can kick around some ideas? In the past when I have 2 workflows, where the outputs of WF1 and inputs to WF2, I have used the Filemanager as the persistence layer between the two. Meaning we ingest the outputs of WF1, then ask WF2 to query the Filemanager for it's inputs. But I think you are asking for something different here. Good luck, -Cameron On Thu, Mar 7, 2013 at 7:41 AM, Cayanan, Michael D (388J) < [email protected]> wrote: > Hi Chris and/or Brian, > > I'm currently on a project where PDS and AMMOS are joining forces to > create a pipeline service and we'd like to use the latest Workflow2 to do > that. They asked a question at last week's meeting regarding if the latest > and greatest OODT Workflow will be able to do state persistence. I can let > Paul Ramirez chime in any further details since he was at the meeting as > well, but can the latest and greatest Workflow do that? And if so, under > which engine? I'm currently using the following engine: > > workflow.engine.factory = > org.apache.oodt.cas.workflow.engine.ThreadPoolWorkflowEngineFactory > > > Thanks, > > Mike > > > > -- Sent from a Tin Can attached to a String
