openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Donald Woods (JIRA)" <j...@apache.org>
Subject [jira] Updated: (OPENJPA-1010) Instantiate meta-model classes for JPA 2.0 from source code annotations
Date Tue, 22 Sep 2009 19:14:16 GMT

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

Donald Woods updated OPENJPA-1010:
----------------------------------

    Affects Version/s:     (was: 2.0.0)
        Fix Version/s:     (was: 2.0.0-M4)
                           (was: 2.0.0)

> Instantiate meta-model classes for JPA 2.0 from source code annotations
> -----------------------------------------------------------------------
>
>                 Key: OPENJPA-1010
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1010
>             Project: OpenJPA
>          Issue Type: New Feature
>          Components: jpa
>            Reporter: Pinaki Poddar
>            Assignee: Pinaki Poddar
>             Fix For: 2.0.0-M3
>
>   Original Estimate: 672h
>  Remaining Estimate: 672h
>
> JPA 2.0 has introduced a specification for strictly-typed dynamic query construction.
The type-strictness is based on availability of a meta-model. The user application can either
use meta-model API to access the type information or instantiate the meta-model (referred
as canonical meta-model) with a set of auto-generated classes for compile-time binding. This
issue refers to instantiating the canonical meta-model at compile-time. 
> The process involves processing source code annotations or xml descriptors. 
> Source code annotation processing support in Java platform has significantly changed
across JDK version 5 and 6. In JDK5, the annotation processing was supported by a command-line
tool named apt based on com.sun.mirror API library. In JDK 6, the annotation processing is
more seamlessly integrated with javac compilation process with javax.annotation API libraries.

> While it is possible, albeit more complex, to support both style (they are not only based
on different libraries, their life-cycle is somewhat different too), at this stage we will
scope this activity to support only JDK 6 environment i.e. we assume that the user application
compiles with a JDK6 compiler.

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