On Mon, Apr 4, 2011 at 1:13 PM, Markus Joschko <[email protected]> wrote: > Hi, > I have a node that should mix free and and fixed properties. > For that purpose I created the following nodetype (leaving out the namespace): > > [Contact] > nt:unstructured, mix:created, mix:lastModified > - primaryContactDetails (weakreference) > > [Individual] > Contact > > > When I create a node of type Individual and set the > primaryContactDetails property to another referencable node, it gets > the typ "reference". > Asked for its required type the property returns "undefined" and as > the DeclaringNodeType it returns "nt:unstructured". > > When I remove "nt:unstructured" from the inheritance list, I get the > desired "weakreference" and Contact as DeclaringNodeType. > > Obviously "nt:unstructure" takes precedence over the defined > properties.
no, named definitions should take precedence over residual definitions. weak reference were introduced in jsr-283 (jcr 2.0). you probably encountered a problem that is specific to weakreferences. do you mind filing a jira issue? a simple test case would be great :) cheers stefan > Is there an other way to combine defined and undefined > properties in a node? > > I currently use jackrabbit 2.1.1 > > > Regards, > Markus >
