[
https://issues.apache.org/jira/browse/AIRAVATA-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Marru resolved AIRAVATA-414.
-----------------------------------
Resolution: Fixed
Fix Version/s: 0.4-INCUBATING
XBaya refactoring seems to be in good shape for now. Closing the issue.
> Refactor XBaya
> --------------
>
> Key: AIRAVATA-414
> URL: https://issues.apache.org/jira/browse/AIRAVATA-414
> Project: Airavata
> Issue Type: Task
> Components: XBaya
> Affects Versions: 0.4-INCUBATING
> Reporter: Saminda Wijeratne
> Assignee: Saminda Wijeratne
> Fix For: 0.4-INCUBATING
>
> Attachments: xbaya-refac.png
>
>
> 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 intended restructuring.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
