Zhao, David wrote:
My last post was little confusing, and I was very confused then, and still kinda now. What I meant was: I've extended Torque Security Service based upon "Torque Security Service Howto" and threads on "Extending User", so I have our own sets of tables, such as person (TURBINE_USER), group (TURBINE_GROUP), role (TURBINE_ROLE), permission (TURBINE_PERMISSION), etc., so I can have additional columns in those tables. However, when I tried to use TurbineSecurity's grant and revoke methods, TURINBE_USER_GROUP_ROLE, and TURBINE_ROLE_PERMISSION are hard-coded in turbine, so I have to use those two tables in Turbine Security schema to store user_group_role and role_permission information, rather than having my own set of tables, am I right on this? I hope this makes sense, and please let me know if there is anything I've done wrong.
Please have a look into the code of GroupPeerManager, PermissionPeerManager, RolePeerManager, UserPeerManager and the associated *Constants classes, where the configuration settings for the TorqueSecurityService can be found. The service can be configured to use whatever Torque-OM-class you may want to use and even contains user definable mappings for the different column and table names.
Bye, Thomas. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
