jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobias Bocanegra (JIRA)" <j...@apache.org>
Subject [jira] Closed: (JCR-474) Introduce 'SecurityConfig' for better extensability.
Date Mon, 03 Jul 2006 14:44:30 GMT
     [ http://issues.apache.org/jira/browse/JCR-474?page=all ]
     
Tobias Bocanegra closed JCR-474:
--------------------------------

    Resolution: Fixed

fixed.

> Introduce 'SecurityConfig' for better extensability.
> ----------------------------------------------------
>
>          Key: JCR-474
>          URL: http://issues.apache.org/jira/browse/JCR-474
>      Project: Jackrabbit
>         Type: Improvement

>   Components: config
>     Versions: 1.0, 1.0.1, 0.9
>     Reporter: Tobias Bocanegra
>     Assignee: Tobias Bocanegra
>     Priority: Minor

>
> the current repository configuration parser parses the security confguration (inluding
appName, AccessManagerConfig and LoginModuleconfig) internally and the passes those 3 values
to the repository config. i suggest to add a new 'SecurityConfig' object that encapsulates
those 3 values and is parsed in a seperate method, in order to allow for better extensability.
this also reduces the size of the alredy bloated repository config constructor.

-- 
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


Mime
View raw message