Hi Sanchit, This understanding counters your proposal altogether. Please read what you have proposed, there is no mention on BPEL/DAG. The native XWF format will give you all the required inputs and your project is about building an interface to efficiently configure inputs, set the workflow execution context and launch it to Workflow Interpreter. This execution interface need not have an understanding of the underlying workflow language. It just needs to understand inputs, and provide intuitive interfaces to provide inputs, specify resources to run the workflow.
Suresh On Jun 1, 2013, at 10:18 AM, Sanchit Aggarwal <[email protected]> wrote: > Hi Suresh > > My understanding on the workflow execution is that the Condor DAG/BPEL > is formed after the composition of the workflow which is than > interpreted by the axis2 based workflow interpreter web service. The > workflow execution context is used to specify the parameters for > scheduling , handling of inputs etc. This execution context is given > from the Xbaya GUI where the context header and other are taken a s a > input. Finally a Executable is formed which is then used for running > the job by GFac. > > So according to the above understanding, I guess The Execution > interface has to be developed which will export the composed workflow > to various workflow languages like BPEL/DAG etc. Please correct me If > I am wrong. > > Since not much has been discussed on the execution interface module of > the master project ,could we have more inputs on the same. > > > > Regards > Sanchit Aggarwal > > > > On Fri, May 31, 2013 at 6:36 PM, Suresh Marru <[email protected]> wrote: >> Sanchit, >> >> Yes lets start the discussion. Please take the lead and post your >> understanding and ask specific questions. >> >> Suresh >> >> On May 31, 2013, at 7:32 AM, Sanchit Aggarwal <[email protected]> >> wrote: >> >>> Hi Heshan/All >>> >>> I am covering workflow execution interface part of the master project >>> in my sub-project.Since the current implementation of the workflow >>> execution context specification is expressed in xml schema encompassed >>> within the workflow wsdl it has to be re-framed. >>> Can we all start discussing here so to get a better understanding of >>> workflow execution context and its representation? >>> >>> Regards >>> Sanchit Aggarwal >>
