The following comment has been added to this issue:
Author: Bob Fleischman
Created: Thu, 10 Jun 2004 2:32 PM
Body:
David:
If I understand things correctly we are going to create a new Group PSML page
(probably called default) and add a property to the JetspeedResources.properties file
similar to
# When a new group is created, this groups's psml is cloned to the new group psml
services.Profiler.newgroup.template=default
What about:
# Setting this account to nothing configures role-based psml as the default method for
new users
I don't think it applies to groups.
Then I need to modify JetspeedProfilerService. I think I need to change public
Profile createProfile(RunData data, Profile profile)throws ProfileException because
that is hard coded with newUserTemplate. Therefore I will probably create
createGroupProfile based upon this method.
Does all that sound correct? Sorry to bother with so much detail, but this is my first
deep foray into changing someone else's code and I want to be sure I'm sticking with
the plan.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/JS1-480?page=comments#action_36021
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/JS1-480
Here is an overview of the issue:
---------------------------------------------------------------------
Key: JS1-480
Summary: Group and Role Profile Default Template Handling
Type: Improvement
Status: Open
Priority: Major
Project: Jetspeed
Components:
PSML
Fix Fors:
1.6-dev
Versions:
1.6-dev
Assignee: David Sean Taylor
Reporter: David Sean Taylor
Created: Mon, 24 May 2004 9:12 AM
Updated: Thu, 10 Jun 2004 2:32 PM
Description:
Bob Fleischman wrote:
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.
...
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
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]