Hi Colm, > I had a similar problem but I wasn't creating groups at runtime so a > restart fixed it... But, from the API docs: > > > Constructor Detail > > AccessControlList > > public AccessControlList(java.util.Map roleSets, > > java.util.Map permissionSets) > > Constructs a new AccessControlList. > > > > This class follows 'immutable' pattern - it's objects can't be modified > > once they are created. This means that the permissions the users have are > > in effect form the moment they log in to the moment they log out, and > > changes made to the security settings in that time are not reflected > > in the state of this object. If you need to reset an user's permissions > > you need to invalidate his session. > > The objects that constructs an AccessControlList must supply hashtables > > of role/permission sets keyed with group objects. > > Did you try logging out and back in?
I had seen that, however the group is created and allocated to a new user (not myself) and then the new user logs in. To my reckoning this should be fine. I can fully understand the need to log out and back in if I was changing my own permissions, but not those of other not currently logged in users. It actually appears that when the first user logs in the ACL structure that will be used for all users is resolved and it is not possible to bring additional groups into effect without the restart. I had a brief look at the source for ACL and couldn't see why this is so. BTW: The API docs for Turbine and Velocity come with the tdk. After you start catalina, surf to http://localhost:8080/ and all will be revealed. Cheers, Scott -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
