|
Home > Archive > Apache JDO Project > July 2006 > Advisory: JDO2 Annotation Metadata
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Advisory: JDO2 Annotation Metadata
|
|
| Craig L Russell 2006-07-22, 7:11 pm |
| | |
| Bin Sun 2006-07-23, 1:11 am |
| +1
> 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
I choose option 1. The class may need to specify
something very specific for JDO in such cases.
Actually, I'd like to see tools invented to convert
EJB3/JPA annotations to JDO annotations in the source
level, if possible.
--- Craig L Russell <Craig.Russell@sun.com> 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!
>
>
________________________________________
__________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
| |
| Ilan Kirsh 2006-07-23, 7:11 pm |
| +1
JDO annotations will override EJB3/JPA annotations.
Ilan
----- Original Message -----
From: "Craig L Russell" <Craig.Russell@Sun.COM>
To: "JDO Expert Group" <jdo-experts-ext@Sun.COM>; "Apache JDO project" <jdo-dev@db.apache.org>
Sent: Sunday, July 23, 2006 1:42 AM
Subject: Advisory: JDO2 Annotation Metadata
> 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!
>
>
| |
| Eric Samson 2006-07-24, 7:11 am |
|
Compliant implementations can optionally use @Entity annotations
instead of JDO annotations
Eric>>>Do you mean supporting EJB3/JPA annotations is enough to be JDO2
compliant?
In that case that's fine with me.
Mapping from EJB3/JPA to JDO will be defined so as to improve
portability of applications from one JDO implementation to others
Eric>>>...and portability between EJB3/JPA and JDO2 implementations...
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
Eric>>>JDO 2 annotations will override EJB3.JPA annotations in this
case.
Best Regards, Eric.
| |
| Michael Bouschen 2006-07-25, 7:11 pm |
| Hi Craig,
+1 Right direction, detailed planning can proceed
JDO annotations will override EJB3/JPA annotations
Regards Michael
> 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!
>
--
Michael Bouschen Tech@Spree Engineering GmbH
mailto:mbo.tech@spree.de http://www.tech.spree.de/
Tel.:++49/30/235 520-33 Buelowstr. 66
Fax.:++49/30/2175 2012 D-10783 Berlin
| |
| Christian Ernst 2006-07-26, 7:11 am |
| Craig L Russell wrote:
> 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:
>
+1
> * JDO annotations will override EJB3/JPA annotations
+1
--
Regards,
Christian Ernst
Versant GmbH, European Headquarters
Wiesenkamp 22b, 22359 Hamburg, Germany
+49(40)60990-338, http://www.versant.com
(CEST, UTC+2)
| |
| Martin Zaun 2006-07-28, 1:11 pm |
|
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!
>
|
|
|
|
|