On Mon, Apr 4, 2011 at 5:29 PM, Alexander Klimetschek <[email protected]> wrote: > On 04.04.11 16:11, "Markus Joschko" <[email protected]> wrote: >>That theoretically means, that a node inheriting from nt:unstructure >>shouldn't have >>any properties because it will always override the catch all of >>nt:unstructure. >>How is validation handled? If my subnode defines a simple string >>property but limits what can be entered. >>Is validation ignored when getting an instance as nt:unstructured or >>is the illusion destroyed? > > If you want that, the primary node type you want to use should not inherit > from nt:unstructured in the first place, and only define the properties > and their constraints that you actually want to allow.
My use case requires a mixed model. I care about 2-3 properties that must be defined. The rest can be freely added by the user. I'll guess I go with nt:unstructure and do all the verification in my application code. Regards, Markus > > Regards, > Alex > > -- > Alexander Klimetschek > Developer // Adobe (Day) // Berlin - Basel > > > > >
