db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig Russell (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JDO-403) JDO2 Annotations
Date Wed, 18 Jul 2007 17:37:05 GMT

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

Craig Russell updated JDO-403:

    Attachment: embedded.patch

I've looked at how to map embedded map keys and values, and by changing the embedded() from
String to @Embedded[ ] and adding embeddedKey, embeddedValue, and embeddedElement to @Field
and @Property, here is some sample code that compiles ok:

    @Field(table="INTEGER_LINES", embeddedKey="true", embeddedValue="true")
                @Field(name="point1.x", column="POINT1_X"),
                @Field(name="point1.y", column="POINT2_Y"),
                @Field(name="point2.x", column="POINT2_X"),
                @Field(name="point2.y", column="POINT2_Y")
    Map<Integer, Line> integerLines;

    @Field (table="LINES", embeddedElement="true")
    @Element (
                @Field(name="point1.x", column="POINT1_X"),
                @Field(name="point1.y", column="POINT2_Y"),
                @Field(name="point2.x", column="POINT2_X"),
                @Field(name="point2.y", column="POINT2_Y")
    Set<Line> lines;

I think it's pretty true to the xml concepts. What do you think?

> 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: annotations.patch, api2_property_table.patch, embedded.patch, embedded.patch,
embedded.patch, fkpk.patch, jdo_2_1_annotations.jar, tck2a.patch, tck2b.patch
> 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.

View raw message