
| Key: |
JS2-211
|
| Type: |
New Feature
|
| Status: |
Closed
|
| Resolution: |
Fixed
|
| Priority: |
Minor
|
| Assignee: |
Ate Douma
|
| Reporter: |
Ate Douma
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
27/Mar/05 07:30 AM
|
|
When a new PA is deployed with several role definitions, these roles still needs to be created by hand
before they can be assigned to a user.
As the required name of these roles (as derived from the web.xml) is predefined, I want to add the feature
to automatically create new RolePrincipals on deployment.
As initial implementation I'm going to use a new jetspeed-portlet.xml meta-data definition: <roles create="true"/>
to enable this feature.
Also, if nobody objects, I'd like to make this the default behavior once this works and then
<roles create="false"/> can be used to prevent it.
|
|
Description
|
When a new PA is deployed with several role definitions, these roles still needs to be created by hand
before they can be assigned to a user.
As the required name of these roles (as derived from the web.xml) is predefined, I want to add the feature
to automatically create new RolePrincipals on deployment.
As initial implementation I'm going to use a new jetspeed-portlet.xml meta-data definition: <roles create="true"/>
to enable this feature.
Also, if nobody objects, I'd like to make this the default behavior once this works and then
<roles create="false"/> can be used to prevent it.
|
Show » |
|
After some thought this didn't seem right because it really wouldn't be meta data in the sense you would
want to store it in the database. Its only a deployment instruction.
I implemented it quite simple now by allowing optional configuration of the PortletApplicationManager.
Just set appropriate values for the roleManager property and autoCreateRoles property.