So (this is for all, guys!)
using role-merge does not seem to save 'space'.
But I still think that role fallback option is meant to function 'on the fly':
is it correct?
That is:
if I do not find a default.psml to clone for a new user, I "fall back" and
show what I find for the defined role.
The matter is: "show" or "clone"?
As Archana says, for multiple role merging, it seems "clone"...
For a single role?
Bye
Stefano
-----Messaggio Originale-----
Da: Archana Turaga
A: Jetspeed Users List
Data invio: giovedì 23 giugno 2005 10.59
Oggetto: RE: Role and default psml
You are right...that will be the result and the PSML will be generated on the
file. If you are doing file-based you should see a new PSML file for the user
that was just created...as much as I remember...since I experimented with this
only once...
-----Original Message-----
From: Stefano Bianchi [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 23, 2005 3:56 AM
To: Jetspeed Users List
Subject: Re: Role and default psml
Dear Archana,
just to get the idea:
if
services.JetspeedSecurity.newuser.roles= ROLE_A, ROLE_B, ROLE_C
and psml for roles are something like:
ROLE_A = {PORTLET_A1, PORTLET_A2, PORTLET_A3}
ROLE_B = {PORTLET_B1, PORTLET_B2}
ROLE_C = {PORTLET_C1, PORTLET_C2, PORTLET_C3}
then the psml for the new user created id something like:
ROLE_A | ROLE_B | ROLE_C
each tab containing the relative portlets.
Correct?
But: the new psml is generated 'on the fly' or is it created by merging the
role psmls and then written on DB/file?
I.E. using roles, can we save DB/harddisk space?
Thanx
Stefano
-----Messaggio Originale-----
Da: Archana Turaga
A: Jetspeed Users List
Data invio: giovedì 23 giugno 2005 10.48
Oggetto: RE: Role and default psml
The psmls from all the roles that were assigned to the user will be
merged...It is actually pretty interesting the way the PSML merge works....if
user has A,B, C roles then the result of the merge is that the PSML belonging
to each user will show up as a separate tab...hope that answers the question...
Regards,
Archana
-----Original Message-----
From: Stefano Bianchi [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 23, 2005 2:27 AM
To: Jetspeed Users List
Subject: Re: Role and default psml
Well, then I hope I am still in time to steal one more:
what does 'role-based merge' mean?
Some portlets from here, some from there?
On which basis?
As a sign of everlasting gratitude, I will post a mail (provide a short
doc?) summarizing this discussion...
Bye
Stefano (Italy)
P.S. Where are you posting from? I see you answer sometimes in the middle
of the night... USA?
-----Messaggio Originale-----
Da: David Sean Taylor
A: Jetspeed Users List
Data invio: giovedì 23 giugno 2005 9.11
Oggetto: Re: Role and default psml
Stefano Bianchi wrote:
> Thank you David!
> You always have the right answer!
> Just some more ;-) (it seems a good opportunity to fix it all for the
> community!):
>
> services.JetspeedSecurity.newuser.roles= user, my_role1, my_role2
>
> Does the new user get ALL these roles?
Yes
> If yes, what does it imply for psml?
If you are using role-based fallback of psml, it means that all roles
psml directories will be searched for a psml resource for the current user
Then there is role-based merge
In that case, when the user is created, then the roles from the
JetspeedSecurity.newuser.roles is applied in merging all role psml
>
> And if
>
> services.Profiler.newuser.template= [blank]
>
> which 'role psml' is used/copied? The first one only (i.e. user)?
> Is the 'role psml' copied as the 'new user's psml' or is it used without
> copying it?
>
only applies when role-based merge is set, again they are all merged
> I hope I have no more, but I can not guarantee!
Don't worry, its good to have questions, especially on these poorly
documented features. Problem is been so busy lately its very difficult
to find time to answer them
David
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This e-mail transmission may contain information that is proprietary,
privileged and/or confidential and is intended exclusively for the person(s) to
whom it is addressed. Any use, copying, retention or disclosure by any person
other than the intended recipient or the intended recipient's designees is
strictly prohibited. If you are the intended recipient, you must treat the
information in confidence and in accordance with all laws related to the
privacy and confidentiality of such information. If you are not the intended
recipient or their designee, please notify the sender immediately by return
e-mail and delete all copies of this email, including all attachments.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This e-mail transmission may contain information that is proprietary,
privileged and/or confidential and is intended exclusively for the person(s) to
whom it is addressed. Any use, copying, retention or disclosure by any person
other than the intended recipient or the intended recipient's designees is
strictly prohibited. If you are the intended recipient, you must treat the
information in confidence and in accordance with all laws related to the
privacy and confidentiality of such information. If you are not the intended
recipient or their designee, please notify the sender immediately by return
e-mail and delete all copies of this email, including all attachments.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
