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 Thu, 07 Jun 2007 17:07:26 GMT

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

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

In addition to the previous addition, please update the provided Field annotation (in the
attached jar) to also include
=====================

    /** Name of the field when this is embedded in another object. */
    String embeddedFieldName() default "";
===================== 

This is for use (only) when the user wants to define the field mapping for embedded fields.
To give an example of its usage

@PersistenceCapable
public class Computer
{
    @Field
    @Embedded(nullIndicatorColumn="GRAPHICS_MANUFACTURER", ownerField="computer",
        fields={
            @Field(embeddedFieldName="manufacturer", columns={@Column(name="GRAPHICS_MANUFACTURER")}),
            @Field(embeddedFieldName="type", columns={@Column(name="GRAPHICS_TYPE")})
        })
    private ComputerCard graphicsCard;
}

@PersistenceCapable
public class ComputerCard
{
    @Field
    private String manufacturer;

    @Field
    private int type;
}

so we are defining the mapping of the columns of ComputerCard when persisted into the table
for Computer.

> 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
>             Fix For: JDO 2 maintenance release 1
>
>         Attachments: 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