jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christophe Lombart" <christophe.lomb...@gmail.com>
Subject Re: [OCM] The ocm:discriminator
Date Thu, 07 Feb 2008 19:21:22 GMT
Why not. it is a good suggestion.

Christophe

On Feb 7, 2008 6:09 PM, Padraic Hannon <pih@wasabicowboy.com> wrote:

> 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 <lukin@stu.cn.ua> 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
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message