You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "J.W. Janssen (JIRA)" <ji...@apache.org> on 2012/11/22 10:32:59 UTC
[jira] [Updated] (FELIX-3777) Make RoleRepository interface more
flexible regarding its implementations
[ https://issues.apache.org/jira/browse/FELIX-3777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
J.W. Janssen updated FELIX-3777:
--------------------------------
Description:
The RoleRepository API is not as flexible as one should want, it is not possible to supply custom implementations of roles (if one really should desire), and the use of IOException leads to lots of (unnecessary) exception wrapping for most implementations.
Also, is it still necessary to have an initialize and close method?
was:The RoleRepository API is not as flexible as one should want, it is not possible to supply custom implementations of roles (if one really should desire), and the use of IOException leads to lots of (unnecessary) exception wrapping for most implementations.
> Make RoleRepository interface more flexible regarding its implementations
> -------------------------------------------------------------------------
>
> Key: FELIX-3777
> URL: https://issues.apache.org/jira/browse/FELIX-3777
> Project: Felix
> Issue Type: Improvement
> Components: User Admin
> Reporter: J.W. Janssen
> Assignee: J.W. Janssen
>
> The RoleRepository API is not as flexible as one should want, it is not possible to supply custom implementations of roles (if one really should desire), and the use of IOException leads to lots of (unnecessary) exception wrapping for most implementations.
> Also, is it still necessary to have an initialize and close method?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira