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] Resolved: (OPENJPA-995) Migrate existing Criteria Query implementation as OpenJPA extension to prepare for upcoming JPA 2.0 spec changes
Date Tue, 28 Apr 2009 17:05:31 GMT

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

Pinaki Poddar resolved OPENJPA-995.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0-M1

> Migrate existing Criteria Query implementation as OpenJPA extension to prepare for upcoming
JPA 2.0 spec changes
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-995
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-995
>             Project: OpenJPA
>          Issue Type: Task
>            Reporter: Pinaki Poddar
>            Assignee: Pinaki Poddar
>             Fix For: 2.0.0-M1
>
>
> JPA 2.0 spec draft version dated Oct 2008 had proposed a Criteria API. Let us call it
CAPI08.
> Current trunk version of OpenJPA has implemented this API. Let us call this CIMPL08.
> In a recent version of JPA spec submitted to JCP, a new Criteria API has replaced the
previous version. Let this be CAPI09
> Given that OpenJPA has a functioning implementation of the earlier proposal -- we need
to satisfy two objectives
> 1. Adopt CAPI09 which will be formalized shortly. This will requires us to update maven
repository with source code for CAPI09. This will replace CAPI08. 
> 2. Migrate the existing implementation CIMPL08 to a refactored openjpa specific package.

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