airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lahiru Gunathilake (JIRA)" <>
Subject [jira] [Updated] (AIRAVATA-629) GFacParameterTypes schema is not w3c schema complaint
Date Mon, 08 Apr 2013 16:47:16 GMT


Lahiru Gunathilake updated AIRAVATA-629:

    Fix Version/s:     (was: 0.7)
> GFacParameterTypes schema is not w3c schema complaint
> -----------------------------------------------------
>                 Key: AIRAVATA-629
>                 URL:
>             Project: Airavata
>          Issue Type: Bug
>          Components: GFac
>    Affects Versions: 0.5
>            Reporter: Suresh Marru
>             Fix For: 0.8
> GFac schema documents for defining the parameters [1] use identical attribute within
in the same document (with single target namespace). On a first look I see no reason we need
to have like a nested attribute. The goal of these custom input output types is for gfac to
handle input with specialized extensions. This could very well be achieved with wrapping all
input output parameter types as simple types (for defined xml types) and complex types for
any custom types gfac has to support. 
> The fix for this schema only impacts GFac functionally but will break the core functionality.
We need to carefully examine the repercussions and make the schema w3c complaint. The UI's
which set the values will have some impact in choosing the types but there will no functional
> [1]

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:

View raw message