jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Reschke (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1543) Improve reliability of canAddMixin
Date Fri, 18 Apr 2008 11:16:24 GMT

    [ https://issues.apache.org/jira/browse/JCR-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590389#action_12590389

Julian Reschke commented on JCR-1543:

QNodeTypeDefinitionImpl: done

Naming of method: I wanted to avoid canAddMixin, as the method has different semantics compared
to canAddMixin (it just checks one of many things).

> Improve reliability of canAddMixin
> ----------------------------------
>                 Key: JCR-1543
>                 URL: https://issues.apache.org/jira/browse/JCR-1543
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-spi
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>            Priority: Minor
>         Attachments: JCR1543.diff, JCR1543.diff
> The current implementation of canAddMixin in JCR2SPI lacks flexibility. It only consults
the (SPI) node type registry, checking for (1) whether the mixin exists, and (2) whether it
is already present and (3) whether it's consistent with the node's type.
> This is fine for stores where any legal mixin can be added anywhere. It doesn't work
well for stores that are limited in what they can do; for instance when nt:file nodes can
be made mix:versionable, but nt:folder nodes can't.
> Proposal: enhance QNodeTypeDefinition with
>   public Name[] getSupportedMixins();
> where the return value is either null (no constraints or no constraints known), or a
list of mixin types that are supported for this node type.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message