The diagram[1] is attached to the jira[2]. Regards, Saminda
1. https://issues.apache.org/jira/secure/attachment/12527162/xbaya-refac.png 2. https://issues.apache.org/jira/browse/AIRAVATA-414 On Tue, May 15, 2012 at 8:46 AM, Lahiru Gunathilake <glah...@gmail.com>wrote: > +1 for this refactoring.. this will be very useful! > > Lahiru > > On Mon, May 14, 2012 at 9:30 PM, Suresh Marru <sma...@apache.org> wrote: > > > > > On May 14, 2012, at 8:38 PM, Saminda Wijeratne wrote: > > > > > Hi Devs, > > > > > > With continuous additions XBaya has being evolved right now to a state > > where it should be restructured & re-factored in order ease the > > maintenance, readability & reusability. > > > > > > Following are the main goals of this task > > > > > > Extract following components as separate maven modules > > > Workflow Interpreter > > > Workflow Monitoring > > > Create a clear separation between the code for GUI and core > > functionalities (This'll be useful for the XBaya web version) > > > Replace all usages of direct service calls > (Registry/WorkflowInterpreter > > etc.) to go through Airavata-client API (This should help stabilize > > Airavata-client API) > > > Attached is a diagram depicting the restructuring which I'm intending. > > > > > ++1, I think its right time for this refactoring. This might help the > GSoC > > projects also to clearly understand the scope of these modules and make > > concrete progress on their projects. > > > > The diagram does not come through in mailing lists, you may want to > create > > a JIRA and attach to it. > > > > Suresh > > > Thanks, > > > > > > Saminda > > > > > > > > > > > > > -- > System Analyst Programmer > PTI Lab > Indiana University >
