karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Adams (JIRA)" <j...@apache.org>
Subject [jira] [Created] (KARAF-2958) Use of type-converters in Karaf Security Documentation is incorrect
Date Wed, 30 Apr 2014 15:30:17 GMT
Paul Adams created KARAF-2958:
---------------------------------

             Summary: 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
            Priority: Minor


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 defining users and roles.  To ensure consistent
paths across platforms a PropertiesConverter is used however the example itself is broken
because it violates 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 because of the order
of elements.

The XML contains:
    <ext:property-placeholder placeholder-prefix="$[" placeholder-suffix="]"/>
    <type-converters>
        <bean class="org.apache.karaf.jaas.modules.properties.PropertiesConverter"/>
    </type-converters> 

But the type-converters element (per the XSD) must follow the optional description element
and precede any others within the root blueprint element.  Re-ordering the XML like:

    <type-converters>
        <bean class="org.apache.karaf.jaas.modules.properties.PropertiesConverter"/>
    </type-converters> 
    <ext:property-placeholder placeholder-prefix="$[" placeholder-suffix="]"/>

to properly place the ext:property-placeholder element AFTER the type-converters 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#a4033003



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

Mime
View raw message