Although jackrabbit supports this, Magnolia doesn't. At least it makes an effort to disallow giving two properties entered through the admincentral interface the same name.
Am Montag, 16. April 2007 16:02 schrieb Oliver Lietz: > Am Montag, 16. April 2007 schrieb Grégory Joseph: > > > I think freemarker doesn't in general make a distinction between > > > foo.baz and > > > foo['baz']. Either should return the same value. ie the property > > > or child > > > named 'baz'. In our case either a wrapped NodeData or a wrapped > > > Content. > > > > Then how to deal with nodes which have a child called "bar" AND a > > property with the same name? One of them will have priority, but the > > other one should still be available to the template, how to deal with > > this? > > This is even more tricky: > > Multiple Values Status > Whether this property can have multiple values, meaning that it stores an > array of values, not just one. Note that this "multiple values" flag is > special in that a given node type may have two property definitions that > are identical in every respect except for the their "multiple values" > status. For example, a node type can specify two string properties both > called X, one of which is multi-valued and the other that is not. An > example of such a node type is nt:unstructured. > (http://jackrabbit.apache.org/doc/nodetype/) > > [...] > > O. > > > ---------------------------------------------------------------- > for list details see > http://www.magnolia.info/en/developer.html > ---------------------------------------------------------------- ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/developer.html ----------------------------------------------------------------
