Hi Supun, XBaya is a legacy library which contains both the XBaya UI code and the Workflow Interpreter code. Separating them out in to 2 different libraries has proven too much of work at the moment. There'll also be some stale classes which over the time has lost its use to the system but was not purged.
*XBaya UI features* Create/register/edit/delete applications Compose/register/edit/delete workflows Run workflows Monitor workflow execution View registry tree Amazon tools Globus tools *Workflow Interpreter* Workflow model Workflow Interpreter Workflow interpreter configuration Workflow notification handling Component Invokers (dynamic/gfac) Utils to manage wsdls, xmls, strings, amazon tasks etc. Thus the classes/packages present in the XBaya does not limit to just registry or provenance. Infact these which you've spotted may just be sub package of a feature grouping (eg: Dialogs : registry login, component pallet: application service components). Please be specific on which package you meant. If you are looking for a starting point in XBaya, start by looking at org.apache.airavata.xbaya.XBaya.main(...) method. Regards, Saminda On Thu, Feb 27, 2014 at 3:44 AM, Supun Nakandala <[email protected]>wrote: > Hi All, > > I was trying to understand 0.11 XBaya implementation. There I found two > packages namely registry and provenance. According to my knowledge registry > is the place where all the persistence data is stored. But I don't > understand where provenance is fitting in the application. > > I would appreciate if someone can provide me an insight on their usage and > how they will map to the proposed Airavata 0.12 API. > > Also I found there are some packages like gfac, globus, modifier, > datadrive, interpreter etc which have no usage in other parts of the XBaya > application. > > Thank you > -Supun Nakandala >
