Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <67468306.1222200224699.JavaMail.jira@brutus>
Date: Tue, 23 Sep 2008 13:03:44 -0700 (PDT)
From: "Christophe Lombart (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Created: (JCR-1760) Review the OCM API and annotations to be
 more compliant with JPA
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Review the OCM API and annotations to be more compliant with JPA
----------------------------------------------------------------

                 Key: JCR-1760
                 URL: https://issues.apache.org/jira/browse/JCR-1760
             Project: Jackrabbit
          Issue Type: Improvement
          Components: jackrabbit-ocm
    Affects Versions: 1.5
            Reporter: Christophe Lombart


It should be possible to start smoothly the JPA support. Of course, all JPA features are not necessary in the JCR world. For example, the annotations @Table and @Column are not very useful for OCM :-). Nevertheless, using almost the same API and a subset of the JPA annotations could be a great help for people who knows the JPA specification. 

Here is a list of changes that we can do quickly : 
- Rename the ObjecContentManager into EntityManager and review some method names. 
- Rename the OCM annotations : 
@Node => @Entity 
@Field => @Basic
@Bean => @OneToOne
@Collection => @OneToMany. Furthermore, @Collection is not a good name because it also supporting Maps :-) 

I would like to wait for the JPA query because the upcoming JPA spec will add more flexibility in this area. 

After, we can review in more details the JPA specification and see if there is a real interest to be more conform to this specification.  

What do you think about that ? Please, add your comments. thanks 


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