Nico Klasens wrote: > I really don't like it, but if we really have to keep it to be backwards > compatible for editors then I am fine with enforce="never".
My feelings about the matter are not very strong. I just configured it like this because it though that was most like how it used to be (though I did not realize that people did succeed entering newlines on guitype='string' ). I will check in my proposal later today. If you think your dislike is big enough you can change it. I don't really mind updating builders, and I don't know how many <guitype>string</guitype> are out there. > New Question > > How would a specialization for creationdate look like? Something like > this with a setprocessor throwing an Exception? > > <specialization id="created"> > <default value="now" /> > <setprocessor> > <class name="org.mmbase.datatypes.processors.Readonly" /> > </setprocessor> > </specialization> Yes. I was about to create such an 'Readonly' class indeed. Because now it is mostly defined in the CommitProcessor, which is a bit silly. And your example is excellent for a field with a setprocessor with that behaviour and no commitprocessor. Michiel -- Michiel Meeuwissen mihxil' Peperbus 111 MediaPark H'sum [] () +31 (0)35 6772979 nl_NL eo_XX en_US _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
