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 2007/08/07 21:39:59 UTC
[jira] Resolved: (JCR-1054) Duplicate attribute in BeanDescriptor
and CollectionDescriptor
[ https://issues.apache.org/jira/browse/JCR-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christophe Lombart resolved JCR-1054.
-------------------------------------
Resolution: Fixed
fixed.
> Duplicate attribute in BeanDescriptor and CollectionDescriptor
> --------------------------------------------------------------
>
> Key: JCR-1054
> URL: https://issues.apache.org/jira/browse/JCR-1054
> Project: Jackrabbit
> Issue Type: Bug
> Components: jcr-mapping
> Affects Versions: none
> Reporter: Christophe Lombart
> Assignee: Christophe Lombart
> Fix For: 1.4
>
>
> 2 different attributes are used in BeanDescriptor and CollectionDescriptor to store the jcr type (jcrType and jcrNodeType). JcrNodeType can be removed.
> This imply modifications in the DTD, the pm implementation and the different mapping xml files used for the unit tests.
> Furthermore, it should be nice to use the same name (jcrType) in all descriptors. There is a lot of confusion across the different descriptors. sometime jcrType is used, sometime jcrNodeType is used. I propose to use only jcrType with the following purpose :
> * In the ClassDescriptor, it is used to store the primary node type of the class.
> * In the FieldDescriptor, it is used to store the property type.
> * In the BeanDescriptor it is used to defined the child node type.
> * In the CollectionDescriptor , it is used to defined the child node type.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.