[ http://issues.apache.org/jira/browse/JDO-204?page=comments#action_12357741 ]
Michael Bouschen commented on JDO-204: -------------------------------------- I understand the scenario that the user wants to store instances of different PC types in the collection. This means even with JDK 5 you need to define the field with Collection<Object> in the Java source. The JDO metadata can be more specific when specifying the element-type. All you need is the possibility to specify more than just one element-type. However, I think this can be done using the existing element-type, so I do not see the need for another metadata element such as element-implementation-type. I think the spec could allow that the element-type value is a list of type names, but I'm not sure whether we should require that every JDO implementation needs to support multiple element-types. Maybe this should be an optional feature. The same holds true for multiple type names in field-type. > Need attribute on field element for type > ---------------------------------------- > > Key: JDO-204 > URL: http://issues.apache.org/jira/browse/JDO-204 > Project: JDO > Type: Bug > Components: api20 > Reporter: Michelle Caisse > Assignee: Craig Russell > > Need to supply instantiated type information for Object & Interface fields. -- 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
