I see, you found the solution yourself. I wanted to test few different scenarios before responding to you, but seem you managed to figure it out yourself in the mean time :) By adding mix:referencable you do not loose performance. The reason why you have to do it is the fact that this mixin is no longer implied since we do not add mix:versionable to all nodes by default. Cheers, Jan
On Mon, 2008-06-23 at 17:55 +0200, Will Scheidegger wrote: > I added "mix:referenceable" as supertype to "dataBase". This solved > the problem. Of course I don't know if I'm loosing performance > benefits again this way... > > Regards, > Will > > On 23.06.2008, at 17:43, Will Scheidegger wrote: > > > O.k., after some digging around I had a closer look at the > > custom_nodetypes.xml file and compared the two from Mag 3.5.4 and > > 3.6 M1. The only remarkable difference I could find is in the > > definition of mgnl:contentNode. The Mag 3.6 file lists > > mix:referencable as supertype for this type together with > > nt:hierarchyNode. The old one only lists nt:hierarchyNode as > > supertype. Now I vaguely remember something about a change in > > nodetype definitions in Mag 3.6 to improve performance. Could it be > > that nt:hierarchyNode used to have mix:referencable as supertype and > > now doesn't anymore? > > > > If so I guess this would mean that I have to add mix:referencable as > > supertype to my data nodes. Should I add it to each one? Or should I > > add it to one of their common supertypes? Which one: dataItem, > > dataItemBase, dataBase? > > > > Cheers, > > Will > > > > On 23.06.2008, at 17:21, Will Scheidegger wrote: > > > >> Hm... I thought about this too, because I imported the config from > >> the old installation instead of creating it with the UI. So as last > >> test before I posted this question I removed the config (/modules/ > >> data/config/types/mynode, /modules/data/trees/mynode), all data and > >> recreated it using the GUI... but also the same name. Do you think > >> that this might be the problem? Where are the node type definitions > >> being stored? And how would I add mix:referencable to it? > >> > >> Thanks for the help! > >> > >> -will > >> > >> On 23.06.2008, at 17:10, Jan Haderka wrote: > >> > >>> Hi Will, > >>> is that from a data type you defined yourself manually or via > >>> DataModule > >>> UI? If it is the former, then you need to make sure that you add > >>> mix:referencable to it, if the latter it is most likely a bug. > >>> Cheers, > >>> Jan > >>> > >>> On Mon, 2008-06-23 at 17:03 +0200, Will Scheidegger wrote: > >>>> I'm testing Magnolia 3.6 M1 with a site which uses the data module. > >>>> I'm pretty happy with the speed, but I'm facing a show stopper now. > >>>> The following code works fine on Magnolia 3.5.4 but throws an > >>>> exception in 3.6m1 > >>>> > >>>> The code: > >>>> > >>>> Content itemValues = (Content) matching.next(); > >>>> String itemValuesUUID = itemValues.getUUID(); > >>>> > >>>> The exception: > >>>> > >>>> javax.jcr.UnsupportedRepositoryOperationException > >>>> at org.apache.jackrabbit.core.NodeImpl.getUUID(NodeImpl.java: > >>>> 2830) > >>>> at > >>>> info.magnolia.cms.core.DefaultContent.getUUID(DefaultContent.java: > >>>> 897) > >>>> > >>>> Additional info: The "itemValues" node which is causing the above > >>>> is a > >>>> data module node so it has its own nodetype. > >>>> > >>>> Any ideas anyone? Thanks! > >>>> > >>>> Regards, > >>>> Will > >>>> > >>>> ---------------------------------------------------------------- > >>>> for list details see > >>>> http://documentation.magnolia.info/ > >>>> ---------------------------------------------------------------- > >>> > >>> > >>> ---------------------------------------------------------------- > >>> for list details see > >>> http://documentation.magnolia.info/ > >>> ---------------------------------------------------------------- > >> > >> > >> ---------------------------------------------------------------- > >> for list details see > >> http://documentation.magnolia.info/ > >> ---------------------------------------------------------------- > > > > > > ---------------------------------------------------------------- > > for list details see > > http://documentation.magnolia.info/ > > ---------------------------------------------------------------- > > > ---------------------------------------------------------------- > for list details see > http://documentation.magnolia.info/ > ---------------------------------------------------------------- ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/ ----------------------------------------------------------------
