Details
-
Bug
-
Resolution: Obsolete
-
Major
-
None
-
2.1.5
-
None
-
Linux, Windows, JDK 1.5.0, Tomcat 5.5.15
Description
I developed a Magnolia module that initialize some roles defined in a roles.properies loaded using the utility method ModuleUtil.registerProperties().
During the development i found that only the odd acls for the same repository where correctly imported and visible from the administration interface.
Let me explain, i have a roles.properies similar to this:
arscadmin.acl_config.0.path = /modules/adminInterface/Config/menu
arscadmin.acl_config.0.permissions = 8
arscadmin.acl_config.1.path = /modules/adminInterface/Config/menu/website_arsvivendi
arscadmin.acl_config.1.permissions = 8
arscadmin.acl_config.2.path = /modules/adminInterface/Config/menu/users
arscadmin.acl_config.2.permissions = 0
arscadmin.acl_config.3.path = /modules/adminInterface/Config/menu/about
arscadmin.acl_config.3.permissions = 0
arscadmin.acl_config.4.path = /modules/website_arsvivendi/*
arscadmin.acl_config.4.permissions = 0
The acls n. 0,2,4 where correctly imported an the others not. After some tests i noticed that the same strange behaviour also affect the original magnolia module dms-1.0RC3!