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-806) Support Criteria API for JPA 2.0 - Iteration 1
Date Wed, 17 Dec 2008 19:52:44 GMT

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

Pinaki Poddar resolved OPENJPA-806.
-----------------------------------

    Resolution: Fixed

The support for Criteria API as per the public draft version of JPA 2.0 specification is available.
The basic approach reuses the existing kernel's capability to support JPQL by converting QueryDefinition
to corresponding JPQL String, so the resultant JPQL string is executed as usual by the kernel.
The JPA 2.0 Specification has not yet mandated any equivalence (string based or otherwise)
between a QueryDefinition and a JPQL string.  But an extended OpenJPAQueryBuilder provides
such a conversion from a QueryDefinition to a JPQL string.
The support is available for all constructs defined in Criteria API including new JPQL features
such as KEY(), VALUE() or CASE statements. However, implementation of some  of these new capabilities
in the kernel's query engine is still in progress.

Preliminary documentation has also been added. Due to the evolving status of the specification
in this regard, the documentation mainly refers to the public draft version of the specification
for details.  

> Support Criteria API for JPA 2.0 - Iteration 1
> ----------------------------------------------
>
>                 Key: OPENJPA-806
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-806
>             Project: OpenJPA
>          Issue Type: Sub-task
>          Components: query
>            Reporter: Pinaki Poddar
>            Assignee: Pinaki Poddar
>   Original Estimate: 1344h
>  Remaining Estimate: 1344h
>
> Implement according to Criteria API Spec.
> Iteration 1 will attempt an approach to convert QueryDefinition to a valid JPQL. This
will help easier build-test-verify cycle.
> Iteration 1 may exclude SubQuery and Case statements. 

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