You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Jean-Sebastien Delfino (JIRA)" <tu...@ws.apache.org> on 2006/04/11 22:03:20 UTC
[jira] Created: (TUSCANY-182) Investigate how to best represent
0..n relationships requiring a keyed access in models
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
Reporter: Jean-Sebastien Delfino
Assigned to: Frank Budinsky
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
[jira] Updated: (TUSCANY-182) Investigate how to best represent
0..n relationships requiring a keyed access in models
Posted by "Jean-Sebastien Delfino (JIRA)" <tu...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/TUSCANY-182?page=all ]
Jean-Sebastien Delfino updated TUSCANY-182:
-------------------------------------------
Component: Java SDO Implementation
Moving this issue to the correct component.
> 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
> Reporter: Jean-Sebastien Delfino
> Assignee: Frank Budinsky
>
> 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
[jira] Updated: (TUSCANY-182) Investigate how to best represent
0..n relationships requiring a keyed access in models
Posted by "Kelvin Goodson (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kelvin Goodson updated TUSCANY-182:
-----------------------------------
Component/s: Java SCA Assembly Model
There's too much assumed context in this JIRA description for me to begin to have an idea of how to address this without some expansion of the topic. I'm adding the SCA Assembly model as an additional component to bring this back onto the SCA radar for some input. If this is not the right SCA component, please advise what it should be.
> Investigate how to best represent 0..n relationships requiring a keyed access in models
> ---------------------------------------------------------------------------------------
>
> Key: TUSCANY-182
> URL: https://issues.apache.org/jira/browse/TUSCANY-182
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Assembly Model, Java SDO Implementation
> Reporter: Jean-Sebastien Delfino
> Assignee: Frank Budinsky
> Fix For: Java-SDO-Next
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Updated: (TUSCANY-182) Investigate how to best represent
0..n relationships requiring a keyed access in models
Posted by "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