Grzegorz Czuba wrote:
> Looking in Turbine code, I found, that in order to do it, I must to create
> at LEAST 20 new java files to change.
>
> I think, that it is to much :)
Come on, you are exagerating...
Only one file needs to be changed to make read-only LDAP roles/permissions
possible, which is Role class.
To make administration facility possible, the methods for listing/adding/removing
permissions should be placed in AccessControlBuilder interface, and
properly implemented in TurbineUser and TurbineJndiUser. Then, admin
screens/actions should make use of these.
> Is there a way to get Turbine to use other implementation of Roles and
> Permission instead
> of based on Peer?
Sure.
# This is the module to handle building AccessControlLists
# Default: org.apache.turbine.om.security.DefaultAccessControl
access.control=org.apache.turbine.om.security.DefaultAccessControl
Rafal.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
