[
https://issues.apache.org/jira/browse/AIRAVATA-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560727#comment-13560727
]
Saminda Wijeratne edited comment on AIRAVATA-679 at 1/23/13 2:49 PM:
---------------------------------------------------------------------
Security settings bean interface added[3]. Will have implementation in 0.7.
3.
https://svn.apache.org/repos/asf/airavata/trunk/modules/airavata-client/src/main/java/org/apache/airavata/client/api/SecuritySettings.java
was (Author: samindaw):
Security settings bean interface. Will not be implemented in 0.6.
3.
https://svn.apache.org/repos/asf/airavata/trunk/modules/airavata-client/src/main/java/org/apache/airavata/client/api/SecuritySettings.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
