[
https://issues.apache.org/jira/browse/JDO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507018
]
Andy Jefferson commented on JDO-403:
------------------------------------
You have to have an array of Columns because if the implementation is mapping a
field to multiple Columns then they are needed. e.g java.awt.Color JPOX maps to
4 cols. How do I embed that and specify the mapping if only one column is
available?
Having an array of Columns is not an issue really since with annotations when
the user wants to specify a single column they dont have to put the {}. That is
i.e @Embedded(nullIndicatorColumn="SOUND_MANUFACTURER", ownerField="computer",
fields={
@Field(embeddedFieldName="manufacturer", [EMAIL
PROTECTED](name="SOUND_MANUFACTURER")),
@Field(embeddedFieldName="type", [EMAIL
PROTECTED](name="SOUND_TYPE"))
})
> JDO2 Annotations
> ----------------
>
> Key: JDO-403
> URL: https://issues.apache.org/jira/browse/JDO-403
> Project: JDO
> Issue Type: New Feature
> Components: api2
> Affects Versions: JDO 2 final
> Reporter: Andy Jefferson
> Assignee: Michelle Caisse
> Fix For: JDO 2 maintenance release 1
>
> Attachments: embedded.patch, jdo_2_1_annotations.jar
>
>
> It would be desirable for JDO2 to have its own set of annotations. We have
> developed a set within JPOX that would likely serve as a starting point for
> such a set. In my opinion they should be
> 1. Split into javax.jdo.annotations.jdo and javax.jdo.annotations.orm
> 2. Move ORM attributes from some of the JDO annotations and have a ORM
> annotation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
