You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Timothy Ward (Created) (JIRA)" <ji...@apache.org> on 2011/12/06 21:03:39 UTC

[jira] [Created] (ARIES-799) Aries Repository Generation does not respect blueprint collection semantics

Aries Repository Generation does not respect blueprint collection semantics
---------------------------------------------------------------------------

                 Key: ARIES-799
                 URL: https://issues.apache.org/jira/browse/ARIES-799
             Project: Aries
          Issue Type: Bug
            Reporter: Timothy Ward


The Aries Application runtime allows blueprint applications to be modelled and stored in OBR repository syntax. This doesn't honour some of the infromation stored in the blueprint service properties. If the service declares a list or set as a property value, this is modelled (incorrectly) as an array. This also causes problems where duplicate values are included in arrays that were supposed to be sets!

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

        

[jira] [Assigned] (ARIES-799) Aries Repository Generation does not respect blueprint collection semantics

Posted by "Timothy Ward (Assigned) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ARIES-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Ward reassigned ARIES-799:
----------------------------------

    Assignee: Timothy Ward
    
> Aries Repository Generation does not respect blueprint collection semantics
> ---------------------------------------------------------------------------
>
>                 Key: ARIES-799
>                 URL: https://issues.apache.org/jira/browse/ARIES-799
>             Project: Aries
>          Issue Type: Bug
>            Reporter: Timothy Ward
>            Assignee: Timothy Ward
>
> The Aries Application runtime allows blueprint applications to be modelled and stored in OBR repository syntax. This doesn't honour some of the infromation stored in the blueprint service properties. If the service declares a list or set as a property value, this is modelled (incorrectly) as an array. This also causes problems where duplicate values are included in arrays that were supposed to be sets!

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

        

[jira] [Resolved] (ARIES-799) Aries Repository Generation does not respect blueprint collection semantics

Posted by "Timothy Ward (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ARIES-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Ward resolved ARIES-799.
--------------------------------

    Resolution: Fixed
    
> Aries Repository Generation does not respect blueprint collection semantics
> ---------------------------------------------------------------------------
>
>                 Key: ARIES-799
>                 URL: https://issues.apache.org/jira/browse/ARIES-799
>             Project: Aries
>          Issue Type: Bug
>            Reporter: Timothy Ward
>            Assignee: Timothy Ward
>
> The Aries Application runtime allows blueprint applications to be modelled and stored in OBR repository syntax. This doesn't honour some of the infromation stored in the blueprint service properties. If the service declares a list or set as a property value, this is modelled (incorrectly) as an array. This also causes problems where duplicate values are included in arrays that were supposed to be sets!

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