Mailing-List: contact jackrabbit-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jackrabbit-dev@incubator.apache.org
Message-ID: <348875670.1123788234562.JavaMail.jira@ajax.apache.org>
Date: Thu, 11 Aug 2005 21:23:54 +0200 (CEST)
From: "Brian Moseley (JIRA)" <jira@apache.org>
To: jackrabbit-dev@incubator.apache.org
Subject: [jira] Commented: (JCR-185) filter jcr properties in jcr-server
In-Reply-To: <855542854.1123724142519.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/JCR-185?page=comments#action_12318529 ] 

Brian Moseley commented on JCR-185:
-----------------------------------

DavResourceImpl should also honor the ResourceFilter when setting and removing properties.

> filter jcr properties in jcr-server
> -----------------------------------
>
>          Key: JCR-185
>          URL: http://issues.apache.org/jira/browse/JCR-185
>      Project: Jackrabbit
>         Type: Improvement
>     Reporter: Brian Moseley
>     Priority: Minor
>  Attachments: property-filtering.patch
>
> attached is a patch that implements jcr property filtering in jcr-server in the same way that nodes and resources are filtered. with the default filter configuration, this has the effect of filtering jcr:created, jcr:mixinTypes, and jcr:primaryType from nt:folder and nt:file nodes. 
> this is likely the expected default behavior for most webdav servers - they want to return the normal dav properties, live properties defined themselves, and dead properties defined by clients, but not jcr-internal properties which are for all intents and purposes implementation-specific.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira