A while ago there was a conversation in which Christophe mentioned a
desire to drop ocm:desciminator
http://markmail.org/message/hg7qe4a442sl34ky?q=ocm:discriminator
FYI, I would like to drop the ocm:discriminator. It is used when the
same
node type is applied on a complete java class hierarchy in order to
find the
appropriate descendant class when a new object has to be
instantiated. It is
tedious to support it just to solve this issue.
Has anyone given this more thought? If no one objects I'll open a Jira
ticket and work on a patch, I think we could just use the mapping file
and node type. This would mean we would loose the ability to map
multiple classes to a single node type/mixin set, but I am unsure if
that is such a bad thing anyway.
-paddy
