Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jdo-dev@db.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Date: Fri, 28 Jul 2006 07:32:05 -0700
From: Martin Zaun <Martin.Zaun@Sun.COM>
Subject: Re: Advisory: JDO2 Annotation Metadata
In-reply-to: <4D1586C5-AE43-418A-82F1-F9C77F4FA88E@Sun.COM>
Sender: Martin.Zaun@Sun.COM
To: jdo-dev@db.apache.org, JDO Expert Group <jdo-experts-ext@Sun.COM>
Message-id: <44CA1FE5.3070506@sun.com>
Organization: Sun Microsystems, Inc.
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7BIT
References: <d391061f4b3376d9af2b8ee212c41c14@webmail.plus.net>
 <200607050848.02232.andy@jpox.org>
 <C22C0529-74FF-478E-BBF8-ADF5070C6A5C@SUN.com> <44C0B5BD.6000706@versant.com>
 <4D1586C5-AE43-418A-82F1-F9C77F4FA88E@Sun.COM>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.13)
 Gecko/20060414


Hi Craig,
+1 Right direction, detailed planning can proceed
JDO annotations will override EJB3/JPA annotations

I wouldn't mind if all annotations were declared in one package
   javax.jdo.annotation
they could still be specified/described as two distinctive sets
(domain object model and mapping metadata).

Martin

Craig L Russell wrote:
> I'd like to get a sense of the community on this proposal based on  the 
> recent discussion on the alias. Please provide some feedback.  This 
> would be for a JDO 2.1 Maintenance Release.
> 
> [+1] Right direction, detailed planning can proceed
> 
> [-1] We need something different (please specify the direction)
> 
> Proposal:
> 
> JDO2 will define a complete set of annotations
> 
> Annotations will be declared in two different packages; jdo  annotations 
> would contain only object model metadata, not mapping  metadata:
>  * javax.jdo.annotation.jdo
>  * javax.jdo.annotation.orm
> 
> Annotation documentation will focus on mapping between annotations  and 
> the existing xml metadata and will use the identical semantics of  xml 
> metadata
> 
> Compliant implementations that support JDK1.5 will be required to  
> accept annotated classes' metadata
> 
> If annotated classes are used with xml metadata, xml metadata will  
> override annotation metadata.
> 
> JDO2 will define interoperability with EJB3/JPA annotations
> 
> Compliant implementations can optionally use @Entity annotations  
> instead of JDO annotations
> 
> Mapping from EJB3/JPA to JDO will be defined so as to improve  
> portability of applications from one JDO implementation to others
> 
> If both JDO and EJB3/JPA annotations are used in the same class we  need 
> to choose between:
> 
>  * JDO annotations will override EJB3/JPA annotations
>  * This is illegal
> 
> Craig Russell
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>