portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Commented: (JS2-64) User Attributes - J2 Extension
Date Sat, 05 Jun 2004 20:09:53 GMT
The following comment has been added to this issue:

     Author: David Le Strat
    Created: Sat, 5 Jun 2004 1:08 PM
       Body:
Started implementation. Completed first phase, i.e. loading xml mapping into the registry.

Some refactoring was made to remove from common registry specific items:
- Move from DublinCoreImpl, LocalizedFiledImpl and GenericMetadataImpl from common to registry.

Next step: implement the logic to map user-attribute name to user attribute name-link.
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/JS2-64?page=comments#action_35927

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/JS2-64

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JS2-64
    Summary: User Attributes - J2 Extension
       Type: New Feature

     Status: In Progress
   Priority: Major

    Project: Jetspeed 2
   Fix Fors:
             2.0-dev/cvs
   Versions:
             2.0-dev/cvs

   Assignee: David Le Strat
   Reporter: David Le Strat

    Created: Wed, 2 Jun 2004 6:28 PM
    Updated: Sat, 5 Jun 2004 1:08 PM

Description:
In the current portlet specs, there is no capability for mapping ref to link for user attributes
between a portlet and the portal implementation.

In a portlet application, we can specify which user attribute the portlet will use.  For instance:

<user-attribute>
    <description>User Given Name</description>
    <name>user.name.given</name>
</user-attribute>

where user.name.given is the name of the attribute in the portal and the portlet.  But what
if, we want to deploy prebuilt portlets in J2 which leverage user attribute but the portlet
code user is user-name-given instead of user.name.given used by the portal.

It therefore seems to me, that the same way security mapping has a role-name and a role-link,
the same should apply to user attribute.

I am proposing that we leverage jetspeed-portlet.xml to support such a mapping.  If no mapping
is specified then the default behavior takes place, if a mapping is specified in jetspeed-portlet.xml,
J2 will leverage that mapping as a way to map J2 user attributes to the portlet user attribute
(in the example above, user-name-given to user.name.given).



---------------------------------------------------------------------
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: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org


Mime
View raw message