You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Jeremy Bauer (JIRA)" <ji...@apache.org> on 2010/01/18 21:12:54 UTC

[jira] Closed: (OPENJPA-757) Map existing OpenJPA extensions to new features of JPA 2.0

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

Jeremy Bauer closed OPENJPA-757.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0
         Assignee: Jeremy Bauer

> Map existing OpenJPA extensions to new features of JPA 2.0
> ----------------------------------------------------------
>
>                 Key: OPENJPA-757
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-757
>             Project: OpenJPA
>          Issue Type: Task
>          Components: jpa
>    Affects Versions: 2.0.0-M2
>            Reporter: Jeremy Bauer
>            Assignee: Jeremy Bauer
>             Fix For: 2.0.0
>
>
> This task is to map new features/functionality provided by JPA 2.0 to functionality already provided by OpenJPA extensions.  For example, mapping the OpenJPA cache to the Cache interface defined by JPA 2.0.   Some functions may map fairly well to existing extensions while others may need additional work.  The most current draft of JSR-317 (http://jcp.org/aboutJava/communityprocess/edr/jsr317/) should be used when making evaluations.  Comments/attachments should indicate the version of the spec used when doing the evaluation.  This mapping can be done piecemeal and then pulled together to form a comprehensive list/evaluation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.