[
https://issues.apache.org/jira/browse/AIRAVATA-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13263744#comment-13263744
]
Raminderjeet Singh edited comment on AIRAVATA-401 at 4/27/12 3:33 PM:
----------------------------------------------------------------------
This is really good thing to do. it may be a good idea to change the schema so
that user can mark input parameters as optional. Just allowing empty or null
parameters can create problems like clients setting null value but user
consider its a mandatory for the application to run. similar requirement
applies to outputs also.
was (Author: raminder):
This is really good thing to do. it may be a good idea to change the schema
so that user can mark input parameters as optional. Just allowing empty or null
parameters can create problems like clients setting null value but user
consider its a mandatory filed for the application. similar requirement applies
to outputs also.
> Allowing users to give empty String and URL inputs for a workflow
> -----------------------------------------------------------------
>
> Key: AIRAVATA-401
> URL: https://issues.apache.org/jira/browse/AIRAVATA-401
> Project: Airavata
> Issue Type: Improvement
> Components: XBaya
> Affects Versions: 0.1-INCUBATING
> Environment: mac
> Reporter: Lahiru Gunathilake
> Fix For: 0.4-INCUBATING
>
>
> There are use cases where users wants to provide empty input values for input
> types like String and URL. Currently GFac doesn't support null or empty input
> values.
> Lahiru
--
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
