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-1091) more lenient behavior of Node#addMixin if mixin is already present
Date Mon, 27 Aug 2007 15:39:30 GMT

    [ https://issues.apache.org/jira/browse/JCR-1091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523031

Julian Reschke commented on JCR-1091:

Proposal for next steps:

JCR2SPI: mirror the change in jackrabbit-core.

TCK: unless JSR170 is changed, do not rely on the lenient behaviour; instead add a convenience
method that checks whether adding a mixin type is needed, and use that throughout. As in:

public boolean needsMixin(Node n, String mixin) {
  return ! n.getSession().getWorkspace().getNodeTypeManager().getNodeType(n.getNodeType()).isNodeType(mixin);

> more lenient behavior of Node#addMixin if mixin is already present 
> -------------------------------------------------------------------
>                 Key: JCR-1091
>                 URL: https://issues.apache.org/jira/browse/JCR-1091
>             Project: Jackrabbit
>          Issue Type: Improvement
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>            Priority: Minor
> Change implementation of addMixin() so that it doesn't fail when the mixin is already
> See also:
> jackrabbit core change: <http://svn.apache.org/viewvc?view=rev&revision=570149>
> JSR-283 issue: <https://jsr-283.dev.java.net/issues/show_bug.cgi?id=353>
> (this affects both the TCK and JCR2SPI, so I didn't specify a component)

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

View raw message