Is this what you want? # # Profiler Role-based merge fallback options # # When rolefallback is true and rolemerge is true, new user's profile will # be an aggregate of psml from each role the user is part of. services.Profiler.rolemerge=true
# Controller to use in merged profile services.Profiler.rolemerge.controller=TabController # Control to use in merged profile services.Profiler.rolemerge.control=TabControl Best regards, Mark Orciuch - [EMAIL PROTECTED] Jakarta Jetspeed - Enterprise Portal in Java http://jakarta.apache.org/jetspeed/ > > > 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 > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
