You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by "Saminda Wijeratne (JIRA)" <ji...@apache.org> on 2013/09/24 01:06:02 UTC
[jira] [Resolved] (AIRAVATA-912) [GSoC] JSON equivalent of XWF
files
[ https://issues.apache.org/jira/browse/AIRAVATA-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Saminda Wijeratne resolved AIRAVATA-912.
----------------------------------------
Resolution: Fixed
Fix Version/s: 0.10
Hi Shameera,
I tested you patch on trunk with
- integration tests
- 10 min tutorial
- importing workflows using xbaya
- viewing workflow templates from registry viewer in xbaya
All tests passed & commited the code to trunk.
Committed revision 1525727.
I also noticed that the patch related to "gsoc2013/app/scripts/registryAPI.js" is already commited, thus I didn't do any commit changes to the GSoC sandbox location.
Thank you for the patch.
> [GSoC] JSON equivalent of XWF files
> -----------------------------------
>
> Key: AIRAVATA-912
> URL: https://issues.apache.org/jira/browse/AIRAVATA-912
> Project: Airavata
> Issue Type: Improvement
> Components: Registry API
> Reporter: Subho Banerjee
> Labels: features, gsoc
> Fix For: 0.10
>
> Attachments: AIRAVATA-912_airavataTrunk_updated.patch, AIRAVATA-912_masterProject_updated.patch
>
>
> We need to have an API endpoint to get the JSON equivalent of the XWF file to define the graph corresponding to the workflow.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira