[
https://issues.apache.org/jira/browse/AIRAVATA-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13542350#comment-13542350
]
Saminda Wijeratne commented on AIRAVATA-679:
--------------------------------------------
"WorkflowContextHeaderBuilder" is now hidden under 2 classes called
"WorkflowSchedulingSettings"[1] & "WorkflowOutputDataSettings"[2].
("WorkflowSecuritySettings" will follow). and they are made available through
ExperimentAdvanceOptions bean.
1.
https://svn.apache.org/repos/asf/airavata/trunk/modules/airavata-client/src/main/java/org/apache/airavata/client/api/WorkflowSchedulingSettings.java
2.
https://svn.apache.org/repos/asf/airavata/trunk/modules/airavata-client/src/main/java/org/apache/airavata/client/api/WorkflowOutputDataSettings.java
> Make the WorkflowContextHeaderBuilder transparent to the API User
> -----------------------------------------------------------------
>
> Key: AIRAVATA-679
> URL: https://issues.apache.org/jira/browse/AIRAVATA-679
> Project: Airavata
> Issue Type: Task
> Components: Airavata Client
> Affects Versions: 0.5
> Reporter: Saminda Wijeratne
> Fix For: 0.6
>
>
> Eventhough WorkflowContextHeaderBuilder is a very useful concept when running
> workflows, allowing users to fill in this object can be confusing because,
> 1. The name is confusing
> 2. Different workflow context data in a single class (scheduling/output
> handling/security)
> We need to revamp this to have a more user friendly version for the API.
--
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
