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

Hasitha Aravinda commented on AIRAVATA-343:
-------------------------------------------

Here I have attached current version of the debugger POC. Current 
implementation supports for following nodes.

* WS Components
* Dynamic Components
* IF Components
* For Each Components
* SubWorkflow Component - (Including its sub workflow Nodes)
* And Input and Output Nodes.

Also I updated to sample debugger GUI client at [1] for recent changes. You can 
try current debugger implementation by running it, or by running test case 
WorkflowDebuggingTest  ( added into the Xbaya Test).

Note: Please apply patch to the Xbaya-GUI module and build it, before you try 
sample debugger GUI. Please refer instructions given in previous comment to 
debug a workflow using sample debugger GUI.  

I will continue the development of this module along with the MetCat 
development. Future works of the Debugger module.

* Adding support for Amazon nodes, doWhile node.
* Implementing Debugger support for XBaya.
* Implement Modify data on-fly support.

Hasitha.

[1] - 
https://svn.codespot.com/a/apache-extras.org/airavata-gsoc-sandbox/trunk/hasitha/sampleDebuggerClient

                
> [GSoC] Workflow Debugging Framework for Airavata
> ------------------------------------------------
>
>                 Key: AIRAVATA-343
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-343
>             Project: Airavata
>          Issue Type: New Feature
>          Components: Workflow Interpreter
>            Reporter: Saminda Wijeratne
>            Priority: Minor
>              Labels: gsoc2012, mentor
>         Attachments: debuggerModule_midterm_eval.patch, 
> Xbaya_debugger_support_20_08_2012.patch
>
>
> The backend of Airavata should support workflow debugging. It should expose 
> some API that will enable users to connect & 
> 1. Receive workflow execution data, current state data
> 2. Send commands to manipulate execution life cycle 
> (pause/resume/restart/stop etc.)
> 3. Modify workflow data on the fly
> The API should be intuitive, language independent & supports remote debugging.
> The specifics for the task & the level of debugging is open for discussion.

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

        

Reply via email to