Return-Path: 
 <issues-return-18451-apmail-karaf-issues-archive=karaf.apache.org@karaf.apache.org>
X-Original-To: apmail-karaf-issues-archive@minotaur.apache.org
Delivered-To: apmail-karaf-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 3994910562
	for <apmail-karaf-issues-archive@minotaur.apache.org>;
 Thu,  1 May 2014 17:15:17 +0000 (UTC)
Received: (qmail 22851 invoked by uid 500); 1 May 2014 17:15:16 -0000
Delivered-To: apmail-karaf-issues-archive@karaf.apache.org
Received: (qmail 22806 invoked by uid 500); 1 May 2014 17:15:16 -0000
Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@karaf.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@karaf.apache.org>
List-Post: <mailto:issues@karaf.apache.org>
List-Id: <issues.karaf.apache.org>
Reply-To: dev@karaf.apache.org
Delivered-To: mailing list issues@karaf.apache.org
Received: (qmail 22795 invoked by uid 99); 1 May 2014 17:15:16 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 May 2014 17:15:16 +0000
Date: Thu, 1 May 2014 17:15:15 +0000 (UTC)
From: =?utf-8?Q?Jean-Baptiste_Onofr=C3=A9_=28JIRA=29?= <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: <JIRA.12711485.1398871721426.214228.1398964515975@arcas>
In-Reply-To: <JIRA.12711485.1398871721426@arcas>
References: <JIRA.12711485.1398871721426@arcas>
Subject: [jira] [Commented] (KARAF-2958) Use of type-converters in Karaf
 Security Documentation is incorrect
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/KARAF-2958?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1398=
6776#comment-13986776 ]=20

Jean-Baptiste Onofr=C3=A9 commented on KARAF-2958:
---------------------------------------------

Manual code updated, I will publish both karaf-2.3.x and 3.0.x manual on we=
bsite later today.

> Use of type-converters in Karaf Security Documentation is incorrect
> -------------------------------------------------------------------
>
>                 Key: KARAF-2958
>                 URL: https://issues.apache.org/jira/browse/KARAF-2958
>             Project: Karaf
>          Issue Type: Documentation
>          Components: karaf-documentation
>    Affects Versions: 3.0.0
>            Reporter: Paul Adams
>            Assignee: Jean-Baptiste Onofr=C3=A9
>            Priority: Minor
>              Labels: documentation
>             Fix For: 2.4.0, 4.0.0, 3.0.2, 2.3.6
>
>
> The documentation at:
> http://karaf.apache.org/manual/latest/developers-guide/security-framework=
.html
> contains an example of using blueprint to configure a JAAS realm and uses=
 the $[karaf.base] property to specify the path to the properties file defi=
ning users and roles.  To ensure consistent paths across platforms a Proper=
tiesConverter is used however the example itself is broken because it viola=
tes the XML XSD for http://www.osgi.org/xmlns/blueprint/v1.0.0.
> The example XML will not deploy complaining of an XML schema violation be=
cause of the order of elements.
> The XML contains:
>     <ext:property-placeholder placeholder-prefix=3D"$[" placeholder-suffi=
x=3D"]"/>
>     <type-converters>
>         <bean class=3D"org.apache.karaf.jaas.modules.properties.Propertie=
sConverter"/>
>     </type-converters>=20
> But the type-converters element (per the XSD) must follow the optional de=
scription element and precede any others within the root blueprint element.=
  Re-ordering the XML like:
>     <type-converters>
>         <bean class=3D"org.apache.karaf.jaas.modules.properties.Propertie=
sConverter"/>
>     </type-converters>=20
>     <ext:property-placeholder placeholder-prefix=3D"$[" placeholder-suffi=
x=3D"]"/>
> to properly place the ext:property-placeholder element AFTER the type-con=
verters element resolves the problem and allows it to deploy properly.
> See the nabble thread on the topic:
> http://karaf.922171.n3.nabble.com/Jaas-realm-problem-td4031391i20.html#a4=
033003



--
This message was sent by Atlassian JIRA
(v6.2#6252)