jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christophe Lombart (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-1759) Simplify the usage of OCM annotations
Date Sat, 27 Sep 2008 12:47:44 GMT

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

Christophe Lombart resolved JCR-1759.

       Resolution: Fixed
    Fix Version/s: 1.5

Now, it is simpler to define the mapping for abstract classes, inheritance tree and persistent
classes that implement interfaces. 

See an example in the unit test: 




> Simplify the usage of OCM annotations
> -------------------------------------
>                 Key: JCR-1759
>                 URL: https://issues.apache.org/jira/browse/JCR-1759
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-ocm
>    Affects Versions: 1.5
>            Reporter: Christophe Lombart
>            Assignee: Christophe Lombart
>             Fix For: 1.5
> If we are using more reflections during the OCM init phase (class descriptor loading),
some OCM annotation settings are not necessary : 
> @Node(isAbtract=true) : used to specify an abstract classes
> @Node(extend=....) : used to specify the ancestor class
> @Node(isInterface= ...) : used to specify the entity as an interface
> @implement  : used to specify the associated interfaces
> If this refactoring is done, we can set them as deprecated.
> The performances will not suffer because this is done only once during the application
startup (when the ObjectContentManager is initialized). 

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

View raw message