portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Commented: (JS1-480) Group and Role Profile Default Template Handling
Date Thu, 10 Jun 2004 21:33:15 GMT
The following comment has been added to this issue:

     Author: Bob Fleischman
    Created: Thu, 10 Jun 2004 2:32 PM

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

What about:
# Setting this account to nothing configures role-based psml as the default method for new
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:

View the issue:

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
   Fix Fors:

   Assignee: David Sean Taylor
   Reporter: David Sean Taylor

    Created: Mon, 24 May 2004 9:12 AM
    Updated: Thu, 10 Jun 2004 2:32 PM

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

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org

View raw message