It seems that the discriminator is only needed for the case where you
want to map multiple objects to a single node type. Perhaps we can
force its use only for that condition? That would allow many use cases
to exist without the need for registering special mixin types and
without the need for forcing odd data into the repository.
-paddy
On Feb 7, 2008, at 8:23 AM, Christophe Lombart wrote:
Anyway, forget my solution it is not working in all case (of
course). it is
time to go at home.
On Feb 7, 2008 4:08 PM, Alex Lukin <[EMAIL PROTECTED]> wrote:
I think that mixin node for ocm is right solution. You may just hide
ocm:discriminator node type registration
somewhere behind implementation to simplify OCM initialization.
That means the ObjectContentManager can be used only with Jackrabbit
because
node type registration is not standard.
Christophe
