jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ard Schrijvers (JIRA)" <j...@apache.org>
Subject [jira] [Created] (OCM-50) AnnotationDescriptorReader in case of a @Collection annotation incorrectly assumes the nodetype of the collection *elements* should be used for the collection nodes itself
Date Fri, 25 May 2012 15:17:23 GMT
Ard Schrijvers created OCM-50:
---------------------------------

             Summary: AnnotationDescriptorReader in case of a @Collection annotation incorrectly
assumes the nodetype of the collection *elements* should be used for the collection nodes
itself
                 Key: OCM-50
                 URL: https://issues.apache.org/jira/browse/OCM-50
             Project: Jackrabbit OCM
          Issue Type: Improvement
            Reporter: Ard Schrijvers
            Assignee: Ard Schrijvers
             Fix For: 2.0.0


Note that the digester version does correctly use the configured type: Thus for example:

<collection-descriptor fieldName="collection" jcrName="collection" proxy="false"
        elementClassName="org.apache.jackrabbit.ocm.testmodel.C" jcrType="nt:unstructured"
        jcrAutoCreated="false" jcrMandatory="false" jcrOnParentVersion="IGNORE"
        jcrProtected="false" jcrSameNameSiblings="false"/>

correctly uses nt:unstructured for the collection when created, however, 

@Collection(elementClassName=C.class, jcrType="nt:unstructured", jcrOnParentVersion="IGNORE")
private java.util.Collection collection;

does use the nodetype of C.class as the type for the collection to create

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message