Yes. Node is-a Component (not the case at the moment).
On Mon, Sep 9, 2013 at 12:00 AM, Supun Kamburugamuva <[email protected]>wrote: > You mean Node is a Component or other way around? > > Supun.. > > > On Sun, Sep 8, 2013 at 2:04 PM, Danushka Menikkumbura < > [email protected]> wrote: > >> Architecturally, there should have been a "is-a" relationship between >> Node and Component as opposed to current "has-a" relationship, IMO. >> >> Just my 2c. >> >> Danushka >> >> >> On Sun, Sep 8, 2013 at 11:24 PM, Danushka Menikkumbura < >> [email protected]> wrote: >> >>> According to my knowledge, Node is the one that keeps data >>> (configuration for instance). Component facilitates Node connectivity, >>> hence data flow. >>> >>> Thanks, >>> Danushka >>> >>> >>> On Sun, Sep 8, 2013 at 10:48 PM, Supun Kamburugamuva >>> <[email protected]>wrote: >>> >>>> Hi Danushka, >>>> >>>> Thank you for the explanation. >>>> >>>> But I still cannot clearly understand their role. >>>> >>>> Here is my understanding of one path. >>>> >>>> We have a XML file which defines the workflow. Then we create a >>>> WorkFlow model which consists of Nodes, Edges etc. Then each of these Nodes >>>> have a Component. It seems like a one to one mapping between a Node and a >>>> Component. Is it like a class that can be used to store information about a >>>> Node? >>>> >>>> Thanks, >>>> Supun.. >>>> >>>> >>>> >>>> >>>> On Sun, Sep 8, 2013 at 12:50 PM, Danushka Menikkumbura < >>>> [email protected]> wrote: >>>> >>>>> Supun, >>>>> >>>>> AFAIK, those are the logical components of different types that >>>>> collectively form a workflow. Essentially a component has a set of input >>>>> ports (data/control) and a set of output ports (data/control). >>>>> >>>>> A component in a workflow is analogous to a mediator in an ESB for >>>>> instance. >>>>> >>>>> A GUI node in XBaya that defines the graphical representation of a >>>>> workflow node, encapsulates a component. >>>>> >>>>> Hope that helps. >>>>> >>>>> Thanks, >>>>> Danushka >>>>> >>>>> >>>>> On Sun, Sep 8, 2013 at 9:21 PM, Supun Kamburugamuva <[email protected] >>>>> > wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I went through the code to figure out how the Airavata workflow model >>>>>> is created. There is a set of classes under a package called >>>>>> >>>>>> org.apache.airavata.workflow.model.component >>>>>> >>>>>> I couldn't figure out the design rationale behind these classes. >>>>>> >>>>>> Thanks, >>>>>> Supun.. >>>>>> >>>>>> -- >>>>>> Supun Kamburugamuva >>>>>> Member, Apache Software Foundation; http://www.apache.org >>>>>> E-mail: [email protected]; Mobile: +1 812 369 6762 >>>>>> Blog: http://supunk.blogspot.com >>>>>> >>>>>> >>>>> >>>> >>>> >>>> -- >>>> Supun Kamburugamuva >>>> Member, Apache Software Foundation; http://www.apache.org >>>> E-mail: [email protected]; Mobile: +1 812 369 6762 >>>> Blog: http://supunk.blogspot.com >>>> >>>> >>> >> > > > -- > Supun Kamburugamuva > Member, Apache Software Foundation; http://www.apache.org > E-mail: [email protected]; Mobile: +1 812 369 6762 > Blog: http://supunk.blogspot.com > >
