[jira] Updated: (TUSCANY-182) Investigate how to best represent 0..n relationships requiring a keyed access in models

["Jean-Sebastien Delfino (JIRA)" <tu...@ws.apache.org>]

     [ http://issues.apache.org/jira/browse/TUSCANY-182?page=all ]

Jean-Sebastien Delfino updated TUSCANY-182:
-------------------------------------------

    Fix Version: Java-Mx
        Version: Java-Mx

> Investigate how to best represent 0..n relationships requiring a keyed access in models
> ---------------------------------------------------------------------------------------
>
>          Key: TUSCANY-182
>          URL: http://issues.apache.org/jira/browse/TUSCANY-182
>      Project: Tuscany
>         Type: Improvement

>   Components: Java SDO Implementation
>     Versions: Java-Mx
>     Reporter: Jean-Sebastien Delfino
>     Assignee: Frank Budinsky
>      Fix For: Java-Mx

>
> Some of the 0..n relationships in the SCA assembly model should provide a keyed access (e.g get a component by name in a composite).
> We need to investigate the best pattern (which we may want to also implement in our codegenerator) to provide this function:
> - a list with a get(key) method
> - a map (but the map should preserve the sequence of elements)
> We'll have to balance ease of use for adding to and navigating the relationship, ability to implement integrity constraints on the relationship, relationship with best model implementation practices as well as the SDO spectification, and footprint + performance.
> We also need to investigate if there is a way to automatically derive the introduction of this keyed access to a relationship from XSD metadata (xsd:key for example).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira