You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Brian Moseley (JIRA)" <ji...@apache.org> on 2005/12/07 18:58:12 UTC

[jira] Updated: (JCR-185) filter jcr properties in jcr-server

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

Brian Moseley updated JCR-185:
------------------------------

    Attachment: property-filter.patch

this patch implements property filtering against the current HEAD revision without the extra noise of the previous patch (which is now removed).

angela, your previous comment still stands, so i'd like to hear your current thoughts on the issue.


> 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
>     Assignee: angela
>     Priority: Minor
>  Attachments: property-filter.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