[
https://issues.apache.org/jira/browse/AIRAVATA-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13277758#comment-13277758
]
Suresh Marru commented on AIRAVATA-414:
---------------------------------------
This makes total sense. While you are at it, I also recommend only sustaining
the currently supported features of workflow interpreter. And make it as an
example for future when we can go back to 0.3 branch and restore ODE, pegasus,
jython support and so on. So for now, I recommend remove all not actively
supported features and start out slick. As the need and developer interests
grow, the features can be bought back in. That way we keep the learning curve
and maintains low. Butt its very important to preserve the XBaya archtectural
advantage of ability to construct a higher level abstraction, and then in a
modular way translate that to a lower level enactment script, and in a
pluggable way, ability to deploy and execute on various enactment engines.
> 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
> 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
