[
https://issues.apache.org/jira/browse/JDO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509972
]
Andy Jefferson commented on JDO-403:
------------------------------------
Re: @Table, @JoinTable, @SecondaryTable - these were only added after (unnamed)
commercial vendors asked for ORM annotations splitting out, and subsequently
went very quiet when asked whether the updated annotations were to their
satisfaction. My only requirement on separating concerns of JDO and ORM
annotation features is handled by documentation and education. Consequently I
have no problem with you removing them and adding the "table" element of
@PersistenceCapable, @Field since I seem to remember having exactly that at the
start. Let's just do that now please!
Re: @PersistentInterface - added because we have<class> and <interface> in XML.
I have no issue with it being all in one since we have the "class" object and
can easily detect if it is an interface that it is specified on. Similarly
there is @Field and @Property (with virtually the same elements) to match
<field> and <property>
> 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, fkpk.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.
