db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Jefferson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JDO-403) JDO2 Annotations
Date Sat, 23 Jun 2007 04:16:26 GMT

    [ https://issues.apache.org/jira/browse/JDO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507559
] 

Andy Jefferson commented on JDO-403:
------------------------------------

Why @JoinTable, @SecondaryTable, @Table ?
@Table is the equivalent of <class table="...">
@JoinTable is the equivalent of <field table="..."> when the field is a container field
@SecondaryTable is the equivalent of <field table="..."> when the field is not a container
field
They also map directly across to the same annotations in JPA. 
They are not part of @PersistenceCapabale, @Field since they are ORM and there was a time
when some other vendor requested that ORM annotations be kept separate from non-ORM.
@JoinTable, @SecondaryTable have schema/catalog whereas there is no such concept in the XML
since it is desirable to be able to specify the catalog/schema that ANY table is in, whether
it is primary or secondary or join.
Why not just have @Table at class and field level ? because it is clearer to have the annotations
named specific after what they are representing. 
We cant have an @Table element in @Join since then users would HAVE TO specify it (back to
limitations of default values in annotations).

Hope thats clearer :-)

> 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.


Mime
View raw message