You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Christophe Lombart (JIRA)" <ji...@apache.org> on 2008/09/23 23:05:44 UTC
[jira] Assigned: (JCR-1759) Simplify the usage of OCM annotations
[ https://issues.apache.org/jira/browse/JCR-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christophe Lombart reassigned JCR-1759:
---------------------------------------
Assignee: Christophe Lombart
> 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
>
> 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.