jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Moved: (OCM-13) Review the OCM API and annotations to be more compliant with JPA
Date Mon, 27 Apr 2009 15:02:35 GMT

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

Jukka Zitting moved JCR-1760 to OCM-13:

          Component/s:     (was: jackrabbit-ocm)
           Issue Type: Bug  (was: Improvement)
    Affects Version/s:     (was: 1.5.0)
             Workflow: no-reopen-closed, patch-avail  (was: jira)
                  Key: OCM-13  (was: JCR-1760)
              Project: Jackrabbit OCM  (was: Jackrabbit Content Repository)

> Review the OCM API and annotations to be more compliant with JPA
> ----------------------------------------------------------------
>                 Key: OCM-13
>                 URL: https://issues.apache.org/jira/browse/OCM-13
>             Project: Jackrabbit OCM
>          Issue Type: Bug
>            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.

View raw message