Maybe this have already been answered, but here goes...
By default in JetspeedResources.properties,
services.Profiler.newuser.template=turbine
which means that any new users "clone" the default.psml files as it's own.
If you set
services.Profiler.newuser.template=
any new users clone the default.psml files for the role the new users are placed into,
that's great... BUT, if that new user then customizes somthing, it changes the
default.psml file for that role, effecting all the other users under that role, not so
great. BTW, Jetspeed doesn't seem to create any new directory for that user on the
psml/user directory for those customizations to be saved into...
So here is the question, how do I use the role's psml files as the template, but
create a new directory for that user under psml/user, thus keeping his customizations
separate? Seems the most desirable (and obvious) behavior doesn't it? It took me a
while to figure what it was really doing (as described above).
Thanks,
Mike
Gary Lawrence Murphy <[EMAIL PROTECTED]> wrote:
Thanks for the clarification on this, and I hope I can prod you
for a few more questions :)
>>>>> "D" == David Sean Taylor writes:
D> There is another Profiler feature, Role-based fallback. It
D> could work for you, but only if your user has one role, and if
D> your user doesn't have his or her own PSML resource.
I was almost using this method; I had assigned multiple roles so
that's more like your extended fallback ...
D> One option would be to extend Role-based fallback to merge PSML
D> from all of the user's roles. This would require coding.
The composite role trick might work, but just so I'm clear on this, if
a user has only one role, no personal profile will be created, but
doesn't that also mean the person can never edit their configuration?
(or does it mean that, if they do any customizing, they edit the role
for everyone?)
D> Yet another option: when you perform the maintenance functions:
D> add role upon registration, or remove role upon expiration,
D> programmatically remove the the portlets (or references) from
D> their personal PSML page.
This is more or less the Action-based promote-demote process I had
envisaged, only I hadn't considered also modifying their psml; it will
probably come down to this approach since any dynamic role-merging
appears to preclude other personal customizations.
Thanks again for the clarifications.
--
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:
For additional commands, e-mail:
---------------------------------
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now
