openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pinaki Poddar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OPENJPA-1011) Instantiate meta-model classes for JPA 2.0 from XML descriptors
Date Thu, 21 Jul 2011 16:12:00 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069051#comment-13069051
] 

Pinaki Poddar commented on OPENJPA-1011:
----------------------------------------

Kevin,
  For a bug, there has to be code. Right?
  But there is no code for it at all.

 I logged this issue (classify it whichever way you like) to make is
explicit that I am keeping the task i.e. generating this metamodel classes
sourcing the orm.xml rather than annotations  completely out of scope. But
now as the annotation based generation has been stabilized, it is worth to
attempt this task on the basis of what exists in code.

Regards --

Pinaki








From:       "Kevin Sutter (JIRA)" <jira@apache.org>
To:         Pinaki Poddar/Dallas/IBM@IBMUS
Date:       07/21/2011 08:58 AM
Subject:    [jira] [Commented] (OPENJPA-1011) Instantiate meta-model
            classes for JPA 2.0 from XML descriptors




    [
https://issues.apache.org/jira/browse/OPENJPA-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069038#comment-13069038
 ]

Kevin Sutter commented on OPENJPA-1011:
---------------------------------------

In my mind, this JIRA sounds more like a bug than a new feature.  I know
that the generation of the metamodel code is not a requirement of the spec,
but since the orm.xml can provide an entity's meta data, we should be
processing it.

In the mean time, there are a couple of alternatives...  If you are a
WebSphere RAD customer, or even just use Eclipse with the Dali plugin, you
can use the metamodel code generation facility within these tools to
process the orm.xml file.  Depending on your development environment, this
may be an alternative until OpenJPA can update their tooling.

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.
descriptors.
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.
when source code has *no* annotation and persistence meta-data is *only*
available in XML descriptors.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira






> Instantiate meta-model classes for JPA 2.0 from XML descriptors
> ---------------------------------------------------------------
>
>                 Key: OPENJPA-1011
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1011
>             Project: OpenJPA
>          Issue Type: Improvement
>    Affects Versions: 2.0.0
>            Reporter: Pinaki Poddar
>            Assignee: Pinaki Poddar
>            Priority: Critical
>             Fix For: 2.2.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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message