well, you have two scenarios to get this done, based on different criteria:
1. you have the same set of default PSML pages for *all* users, no
matter what roles they are assigned. In this case you can use the
UserDetailsPortlet from the j2-admin portlet app straight away. This
portlet performs a deep copy of all portal resources from a configurable
directory to the new user directory (/_user/<new user>) when you create
a new user. You have to configure the portlet preference
"newUserTemplateDirectory" so it points to the directory holding the
default PSMLs. I believe the default template folder is /_user/template.
2. you want to have default PSMLs *per available role*. This is not
supported out-of-the-box by jetspeed, so you would have to implement
some code by yourself. You can re-use the code from
UserDetailsPortlet.java (for the deep copy part) though. The only thing
you have to do is make the location of the template folder configurable,
based on the default role defined for the new user.
hope this helps you out ?
Dennis
yangwawa wrote:
the first case, I want users to be able to change which portlets are on each
page.
Dennis Dam wrote:
Just to get a clear picture: you want users to be able to change which
portlets are on each page, or you want users to edit the default
configuration of portlets?
yangwawa wrote:
hi,Dennis
Thank u very much for ur reply. It's very kind of u.What I want is
when a new user(A) is created based on role B,the pages under _role/B/ is
deep copied to _user/A/, then the user A can modify his pages freely
without
worrying about affecting others. So which profile rule should be applied
for
the creating of user A.
Regards
Juan Yang
Dennis Dam wrote:
Hi Yang,
please don't email me directly! Always post through the user list
([email protected]), so other people can also benefit
from answers..
to answer your question, you have to use the right profiling rules to
determine the pages a user can see. That depends on your requirements,
do you want users to be able to see pages based on their role, or does
have every user have their own unique pages? Jetspeed is so flexible
with respect to profiling, I can't give you a straight answer unless I
know what you want.
To give an example though, consider the rule "user-role-fallback" which
is mentioned on
http://portals.apache.org/jetspeed-2/guides/guide-profiler.html: this
rule will first look in a user's home dir (/_user/<username>) for a
portal resource (e.g. a psml), and will fall back to role-based lookup
(/_role/<rolename>). So a PSML in the _user/ dir will override a PSML
with the same name in the /_role dir. It sounds like what you want?
Dennis
[EMAIL PROTECTED] wrote:
hi,Dennis
Thank u for ur reply.and I am sorry for my offence.After studying the
resource u gived me before, i am still confused. And now I am trapped
by
the scenario.if I create a folder named after a rolename under
/page/_role/, then when a user of this role type is created, a new
folder
named after the new username is also created under /page/_user/ and
the
content of the new folder is similar to the folder under
/page/_role/rolename. so which profile rule can satisfy my need.thank u
very much.
Regards
Juan Yang
Dennis Dam wrote:
Hi Juan,
The profile rules for a user defines which portal resources (e.g. PSML
pages) are being loaded for the user, based on different criteria. See
http://portals.apache.org/jetspeed-2/guides/guide-profiler.html for a
full explanation.
Dennis
PS The questions you have been asking typically belong to the user
list,
can you post them there from now on?
yangwawa wrote:
hi,all
I have found when admin create a new user he has to choice what the
profile
rule that will be applied into the new user, so how the user profile
affect
the user's character. thank u very much.
Juan Yang
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Quoted from:
http://www.nabble.com/what%27s-the-user-profile-rule-make-sense-tf4856382.html#a13908783
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
