>>>>> "M" == Mark Orciuch <[EMAIL PROTECTED]> writes:
M> Is this what you want? # # Profiler Role-based merge fallback
M> options # # When rolefallback is true and rolemerge is true,
M> new user's profile will # be an aggregate of psml from each
M> role the user is part of. services.Profiler.rolemerge=true
M> # Controller to use in merged profile
M> services.Profiler.rolemerge.controller=TabController
M> # Control to use in merged profile
M> services.Profiler.rolemerge.control=TabControl
This is still basically a one-shot clone operation; the role-based
profile only works if there is only one role, and if that's the case,
then there's no need to merge it.
I think the only viable solution to this problem is programatic: There
needs to be a far more elaborate admin tool which, when it assigns
roles to people, links them to the role profile, and when it removes
roles, cuts the link -- this means the role psml is not customizable
so a secondary, but much more difficult change calls for customizations
to be held seperate from the portlet definition.
That may not be all that difficult: When a user is assigned to a role,
a new portlet is created in their profile, but as a "reference" style
and with no options or parameters; customizations would then be added
to that user-psml such that if the underlining role-psml definition is
altered, options the user /hasn't/ changed would show the change.
--
Gary Lawrence Murphy - [EMAIL PROTECTED] - TeleDynamics Communications
- blog: http://www.teledyn.com/mt/ - biz: http://teledyn.com/ -
"Computers are useless. They can only give you answers." (Picasso)
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
