[
https://issues.apache.org/jira/browse/JDO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508309
]
Andy Jefferson commented on JDO-403:
------------------------------------
> 2. I'd like to talk about mapping org.apache.jdo.tck.pc.mylib.PCRect as an
> embedded field. PCRect includes
> two PCPoint instances, so you have to map the embedded PCPoint instances as
> embedded-embedded
Agreed - nested embedded PC fields aren't catered for in what was provided, and
your example (but using PCRect/PCPoint as nested embedded) demonstrates how it
could be done for 1-level of nesting. XML handles this fine since you can have
<embedded> within a <field> recursively (down to multiple levels). Annotations
have some strange limitation on recursing too (in addition to the other strange
limitations), so not sure if you'll be able to get multi-level recursion (like
XML supports). Its the same issue we have with @FetchGroup and @FetchField
> 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.
