openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Albert Lee (Updated) (JIRA)" <>
Subject [jira] [Updated] (OPENJPA-1011) Instantiate meta-model classes for JPA 2.0 from XML descriptors
Date Thu, 02 Feb 2012 19:38:53 GMT


Albert Lee updated OPENJPA-1011:

    Affects Version/s: 2.2.0
        Fix Version/s:     (was: 2.2.0)

Moved fix version to 2.3.0 in preparation for 2.2.0 release.
> Instantiate meta-model classes for JPA 2.0 from XML descriptors
> ---------------------------------------------------------------
>                 Key: OPENJPA-1011
>                 URL:
>             Project: OpenJPA
>          Issue Type: Improvement
>    Affects Versions: 2.0.0, 2.1.1, 2.2.0
>            Reporter: Pinaki Poddar
>            Assignee: Pinaki Poddar
>            Priority: Critical
>             Fix For: 2.3.0
>   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.
> 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.
> It is not obvious at this point on how to hook into compiler life-cycle when source code
has *no* annotation and persistence meta-data is *only* available in XML descriptors.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message