David:

Thanks. I think this is just what I need. I spent an hour or so trying to
track this back before I posted and hit a few interface dead ends. (I could
find the interface, but not the class which was instantiated.)

I came across exactly the same 2 points you did, which I would like to
improve.

I've some free time over the next few days. I'm going to take a look at this
and see what I can figure out.

Bob

-----Original Message-----
From: David Sean Taylor [mailto:[EMAIL PROTECTED] 
Sent: Monday, May 24, 2004 12:12 PM
To: Jetspeed Users List
Subject: Re: What is the default Group Profile?


On May 21, 2004, at 2:48 PM, Bob Fleischman wrote:

> And where is it created?
>
> I am familiar with services.Profiler.newuser.template for new users,  
> but I
> did not see anything similar for groups.
>
> I would like to intercept the process and customize the Profile/PSML  
> that is
> created for each group so that I can quickly create team workspaces.
>
> Has anyone else tried this??
>
Easy to change the default behavior, see  
o.a.j.services.security.turbine.TurbineGroupManagement.addDefaultGroupPS 
ML, and then see the  
o.a.j.services.profiler.JetspeedProfilerService.createProfile
You can extend these services, or better yet if we can come up with a  
generic solution to your problem, commit it back to CVS head

I noticed 2 issues that can be improved on:

1. The Turbine User (the default User template) was copied over and  
used as a default Group template.
2. The Security constraint applied (owner-only) makes this PSML  
unaccessible

I propose

1. enhancing the TurbineGroupManagement : adding a default Group  
template
2. changing the default security constraint to admin-all / owner-only  
for user resources, and admin-all + particular role or group for new  
group or role resources
This will require creating a new role or group constraint on template  
creation

See JIRA issue:

http://nagoya.apache.org/jira/browse/JS1-480


---------------------------------------------------------------------
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]

Reply via email to