Return-Path: 
 <dev-return-31334-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org>
X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org
Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id D94F92233
	for <apmail-jackrabbit-dev-archive@www.apache.org>;
 Tue,  3 May 2011 10:30:42 +0000 (UTC)
Received: (qmail 37192 invoked by uid 500); 3 May 2011 10:30:42 -0000
Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org
Received: (qmail 37153 invoked by uid 500); 3 May 2011 10:30:42 -0000
Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@jackrabbit.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@jackrabbit.apache.org>
List-Post: <mailto:dev@jackrabbit.apache.org>
List-Id: <dev.jackrabbit.apache.org>
Reply-To: dev@jackrabbit.apache.org
Delivered-To: mailing list dev@jackrabbit.apache.org
Received: (qmail 37146 invoked by uid 99); 3 May 2011 10:30:42 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 May 2011 10:30:42 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 May 2011 10:30:41 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id 26535BFCB3
	for <dev@jackrabbit.apache.org>; Tue,  3 May 2011 10:30:03 +0000 (UTC)
Date: Tue, 3 May 2011 10:30:03 +0000 (UTC)
From: "angela (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: 
 <1214039240.18193.1304418603153.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1173801832.51203.1302568625668.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (JCR-2941) Serialization of privileges should use
 xml namespaces
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ https://issues.apache.org/jira/browse/JCR-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

angela resolved JCR-2941.
-------------------------

    Resolution: Won't Fix

the current format is consistent with the xml-serialization we use(d) to have for node types. in addition you proposal doesn't address the names of the aggregated privileges, where the contains element again defines a name attribute.

> Serialization of privileges should use xml namespaces
> -----------------------------------------------------
>
>                 Key: JCR-2941
>                 URL: https://issues.apache.org/jira/browse/JCR-2941
>             Project: Jackrabbit Content Repository
>          Issue Type: Sub-task
>          Components: security
>    Affects Versions: 2.3.0
>            Reporter: Tobias Bocanegra
>            Assignee: angela
>            Priority: Minor
>             Fix For: 2.3.0
>
>
> the current serialization of privileges does not make use of the namespace capabilities of an xml document. for example
> <?xml version="1.0" encoding="UTF-8"?>
> <privileges xmlns:foo="http://www.foo.com/1.0">
>     <privilege name="foo:testRead"/>
> </privileges>
> the namespace needs to be explicitly defines in the document node, although not used in any of the elements. i think a better format would be:
> <?xml version="1.0" encoding="UTF-8"?>
> <privileges xmlns:foo="http://www.foo.com/1.0">
>     <foo:testRead />
> </privileges>

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira