[ 
https://issues.apache.org/jira/browse/AIRAVATA-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13612438#comment-13612438
 ] 

Andun Sameera Liyanagunawardana commented on AIRAVATA-798:
----------------------------------------------------------

Hi,

I think the purely JavaScript based implementation of Workflow designer will be 
good since we can maintain it without adding other complex dependencies. In my 
internship I have worked in WSO2(www.wso2.com). I have specially worked in 
there ESB which is built on top of Synapse. That ESB have a nice UI with this 
kind of a implementation which is built using purely jQuery. All the 
enterprises service integrations, message flows are designed using this 
sophisticated UI. This is a sample of that UI 
http://docs.wso2.org/wiki/download/attachments/16846268/31.png?version=1&modificationDate=1349302422000.
 They have the same approach Airavata Server and XBaya GUI communicates. 
Front-end UI communicate using API provided by back-end. So because of that 
exposure I think the approach is good. 

Using RapahelJS or KineticJS or YUI will be a handy choice to make our life 
easy. Also cant we have to do lot of changes to API to enable JSON/REST?

Suresh what do you think? What will be the long term plan to move the UI of 
Airavata to web based version?

Thanks
AndunSLG


                
> [GSoC] Web based Workflow Composer for Airavata 
> ------------------------------------------------
>
>                 Key: AIRAVATA-798
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-798
>             Project: Airavata
>          Issue Type: New Feature
>          Components: Workflow Interpreter, XBaya
>            Reporter: Suresh Marru
>              Labels: gsoc2013, mentor
>
> Apache Airavata users construct workflows by chaining together set of 
> applications and web services resulting in a graphical representation of 
> workflows. These workflows composed by drag and drop features build a 
> abstract and high lever workflow languages.Currently Airavata XBaya services 
> these needs and is implemented in Java Swing. Similarly XBaya was also 
> implemented in Flex.
> This project focuses on developing a web based version of the workflow 
> composition and monitoring interface similar in functionality to XBaya. 
> Currently XBaya WSDL operations and message type definition determines both 
> the number of input/output parameters that the component has and the data 
> type of each parameter. Messages are general XML and can have deeply-nested 
> structures.  However, XBaya treats the child elements of the root of a 
> message as independent parameters. The type of each parameter can be any 
> simple type (string, integer, etc.), array, or a complex type. The potential 
> student can evaluate the use of WSDL and come up with alternatives. 
> The student for this task has to be prepared to work extensively in java 
> script to build the drag drop interface. WSDL knowledge will be preferred but 
> not mandatory, that can be acquired. 
> User community & Impact of the software: Airavata is a general purpose 
> distributed systems software. It is used to build science gateways supporting 
> research and education in chemistry, life sciences, biophysics, environmental 
> sciences, geosciences astronomy and nuclear physics. The goal of airavata is 
> to enhance productivity of these gateways to utilize cyberinfrastructure of 
> resources (e.g., local lab resources, the Extreme Science and Engineering 
> Discovery Environment (XSEDE), the Open Science Grid (OSG), University 
> Clusters, Academic and Commercial Computational Clouds like FutureGrid & 
> Amazon EC2). By using open community based software components and services 
> like Airavata, gateways will be able to focus on providing additional 
> scientific capabilities and to expanding the number of supported users. The 
> capabilities of these gateways will offer clear benefits to society.

--
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

Reply via email to